Skip to content

Repository navigation

AGENTS.md: commit through createCommitOnBranch #50

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
rubas-agent merged 1 commit into from
Sep 28, 2026
Merged

AGENTS.md: commit through createCommitOnBranch #50

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,6 +33,12 @@ covers install, the token, and usage.
release. A tag that someone deletes comes back on the next push. To recover a failed build or
release, run `release.yml` through `workflow_dispatch`.

- `main` requires signed commits, and the bot cannot sign a commit. It also cannot read the rule,
so a PR with commits from a plain `git push` shows only `BLOCKED`. Commit through the GraphQL
mutation `createCommitOnBranch`, which GitHub signs: stage the change, then run
`gh-signed-commit "<headline>" ["<body>"]` from rubas/dotfiles. It also creates the branch on
GitHub.

## Pitfalls

- `flake.nix` repeats the package version as a literal. Bump it in the same commit as
Expand Down