Skip to content

Conversation

@masnwilliams
Copy link
Contributor

@masnwilliams masnwilliams commented Jan 21, 2026

Note

Workflow behavior updates

  • update-cli-coverage.yml now checks out the existing cli-coverage-update branch in the CLI repo (if it exists) and merges origin/main into it to keep it current.

Process/instruction changes

  • Step 6 guidance updated to note the branch may already be checked out, use git push origin cli-coverage-update (no force push), and rebase if needed to preserve existing work and history.

Written by Cursor Bugbot for commit 223521c. This will update automatically on new commits. Configure here.

masnwilliams and others added 2 commits January 21, 2026 00:46
The workflow was force-pushing from main, overwriting any existing work
on the cli-coverage-update branch. This change:

- Checks out the existing branch if it exists before making changes
- Merges main into the branch to keep it current
- Instructs the agent to NOT force push, preserving branch history
@masnwilliams masnwilliams merged commit cee2050 into main Jan 21, 2026
5 checks passed
Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.

git fetch origin cli-coverage-update
git checkout cli-coverage-update
# Merge latest main to keep it up to date
git merge origin/main -m "Merge main into cli-coverage-update" --no-edit || true
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Silent merge failure leaves repository in conflicted state

High Severity

The git merge origin/main ... || true silently continues when merge conflicts occur. When a merge fails, the repository is left in a "merging" state with conflict markers in files. The Cursor agent then runs on this corrupted state, which could lead to commits containing conflict markers being pushed, or confusing failures. The merge failure needs explicit handling—either fail the workflow, abort the merge, or resolve conflicts.

Fix in Cursor Fix in Web

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants