diff options
| author | Can Celik <ogulcancelik@gmail.com> | 2026-07-26 04:22:05 +0300 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2026-07-26 04:22:05 +0300 |
| commit | e536bd8bd99de975cb2d15bb384e6e35f88ef88e (patch) | |
| tree | 4de9e0d10c7b0727e693f70b4dbd7859da45f24d /AGENTS.md | |
| parent | 8843bbb0c4dc4e6b52ca5d0a6592ce80be56a19c (diff) | |
fix: support non-us shifted keybindings (#1876)
* fix: support non-us shifted keybindings
refs #1870
* docs: require current pull request base
Diffstat (limited to 'AGENTS.md')
| -rw-r--r-- | AGENTS.md | 2 |
1 files changed, 2 insertions, 0 deletions
@@ -76,6 +76,8 @@ Commit on the task branch in that worktree. For substantive feature and bug-fix work, default to opening a pull request instead of pushing `master` directly. Small, low-risk changes and documentation-only updates can use a lighter workflow when Can prefers it. +Immediately before opening a pull request, fetch `origin` and make sure the task branch is based on the current `origin/master`; rebase it when behind, then rerun relevant validation before pushing. If `master` advances while the pull request is under review and GitHub marks it behind, update the branch and repeat checks and bot review on the new head. + After opening or updating a pull request, monitor all checks to completion with `gh pr checks --watch` or an equivalent command. Treat Greptile and CodeRabbit as part of CI: wait for both to review the latest pushed commit, not only for the build and test jobs to pass. Evaluate every actionable finding. Fix findings you agree with and reply with the fix; reply inline with a concise technical reason when you disagree. After any fix, wait for CI and both review bots again on the new head. When the current pull request head is green and both bot reviews are complete, report that it is ready and stop. Never merge a pull request; Can performs the final merge. |
