Skip to content

Commit

Permalink
docs: Recommend use of "[AGORIC]" comments (#418)
Browse files Browse the repository at this point in the history
  • Loading branch information
gibson042 authored Apr 18, 2024
1 parent e16fe33 commit 5733916
Showing 1 changed file with 2 additions and 0 deletions.
2 changes: 2 additions & 0 deletions Agoric-branch-notes.md
Original file line number Diff line number Diff line change
Expand Up @@ -22,6 +22,8 @@ For new features:

- New features should be landed on `Agoric` first, then cherry-picked to a release branch as needed.
- Create a new development branch off of `Agoric`.
- Make changes, indicating code specific to our fork by ensuring the presence of a preceding or same-line
comment including "[AGORIC]" (e.g., `// [AGORIC] Propagate the event history.`).
- Test, review, merge PR with `automerge` label for mergify.io
- Don't forget to update `CHANGELOG-Agoric.md` with the change and a link to its PR.

Expand Down

0 comments on commit 5733916

Please sign in to comment.