You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add merge conflict detection for pull requests (#12)
When a PR has merge conflicts, GitHub doesn't run workflows, but cimonitor previously didn't report this. Now cimonitor detects and reports merge conflicts using the GitHub API's mergeable state.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-authored-by: Claude <noreply@anthropic.com>
1.`mise run format && mise run lint`, then fix issues
4
+
2.`mise run tests`, then fix issues
5
+
3. Review changes with `git status` and `git diff`, checking for commits vs the merge-base of origin/main, as well as unstaged cahnges, and staged changes
6
+
4. Stage and commit changes:
7
+
8
+
```bash
9
+
git add .# or an appropriate set of files
10
+
git commit -m "$(cat <<'EOF'
11
+
[Your commit message here]
12
+
13
+
🤖 Generated with [Claude Code](https://claude.ai/code)
14
+
15
+
Co-Authored-By: Claude <noreply@anthropic.com>
16
+
EOF
17
+
)"
18
+
```
19
+
20
+
Avoid unnecessary lists in your commit message. Avoid adding filler to lists to make them longer.
🤖 Generated with [Claude Code](https://claude.ai/code)
29
+
EOF
30
+
)"
31
+
```
32
+
33
+
Avoid unnecessary lists in the PR description. PR descriptions do not have a minimum length, just do what's appropriate. Adding fluff and over-emphasizing minor points makes you seem less intelligent.
34
+
7. Monitor CI with `uv run cimonitor watch --pr=<pr-number>`
0 commit comments