docs: style guide in HACKING, new AGENTS.md #242
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
... bringing in Wiki information to the repo, along with a test to create AGENTS.md https://agents.md/
pushing before getting too tired.
Still I'd like @lefessan @nberth @ddeclerck to review the style guide (should not be something new, but maybe I've copied outdated information or missed where ONA broke something) and get to know your opinion on co-coding with agents.
[side story: I've tried that without AGENTS.md on ONA with the suggested "add a testcase for improved coverage" and did not get good results... I may try again soon, both with the testcase and with an addition to XML GENERATE to support OCCURS (I've already made the spec, it should be mostly some refactoring and typing, which the agent may do faster while I do some COBOL work]