Skip to content

docs: add branch protection policy and emphasize mandatory documentat…#43

Merged
ipapadop merged 1 commit into
mainfrom
update-agents-md
Apr 25, 2026
Merged

docs: add branch protection policy and emphasize mandatory documentat…#43
ipapadop merged 1 commit into
mainfrom
update-agents-md

Conversation

@ipapadop
Copy link
Copy Markdown
Owner

…ion updates in AGENTS.md

@ipapadop ipapadop merged commit e38f201 into main Apr 25, 2026
4 checks passed
@ipapadop ipapadop deleted the update-agents-md branch April 25, 2026 13:10
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the AGENTS.md file to enforce a strict source control policy prohibiting direct commits to the main branch and strengthens the requirement for documentation updates after every change. Feedback suggests refining the documentation rule to include 'as necessary' to account for internal changes that do not impact the project's public state or interface.

Comment thread AGENTS.md
- **Verification**: All changes must be verified by ensuring that all tests pass (`ctest`).
- **Project Documentation**: After any code changes, `README.md` and `AGENTS.md` must be reviewed and updated if necessary to reflect the current state of the project.
- **Source Control**: NEVER commit directly to the `main` branch. Always use feature branches and pull requests for any changes.
- **Project Documentation**: After EVERY change, `README.md` and `AGENTS.md` MUST be reviewed and updated to reflect the current state of the project.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The requirement to update documentation after EVERY change is logically problematic for changes that do not affect the project's state or interface (e.g., internal refactoring or fixing typos in comments). While the emphasis on documentation is important for an agent-based project, requiring an update when none is applicable can be confusing. It is better to specify that the files must be reviewed and updated as necessary to reflect the current state.

Suggested change
- **Project Documentation**: After EVERY change, `README.md` and `AGENTS.md` MUST be reviewed and updated to reflect the current state of the project.
- **Project Documentation**: After every change, `README.md` and `AGENTS.md` MUST be reviewed and updated as necessary to reflect the current state of the project.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant