Skip to content

AGENTS.md: add a pushing section #2

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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
lingrui96 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

AGENTS.md: add a pushing section #2

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
14 changes: 14 additions & 0 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -42,6 +42,20 @@ hardware fields in `run.yaml` carry the identity.
move all the crates together, and never mix backend features across them. A bump
can change measured numbers, so it belongs in its own commit with a rerun.

## Pushing

Work lands on main through a pull request rather than a direct push. An agent
may push a branch and open the pull request when asked to, and the merge stays
a human decision. Force push only while a branch is still unreviewed: after
someone has reviewed, a force push detaches their comments from the code they
describe.

A pull request that adds or replaces `result/<profile>/` states in its
description which machine produced the sweep, so the numbers are reviewed
together with the hardware behind them. Keep hostnames out of the description
as well as out of the files: on a public repository a hostname leaks the
operator's institution and location over time.

## Prose style

No em dashes or en dashes anywhere in this repository's documents, comments or
Expand Down
Loading