Conversation
Collaborator
|
This seems like it deserves more of a community discussion. I know you're not generally available during Parsons Parties, do you want to coordinate a separate time to have a discussion? |
Collaborator
Author
|
I can schedule myself to be available, maybe next Thursday? |
Collaborator
|
The 10th? That works for me |
Added comprehensive agent instructions covering scope, sources of truth, handling ambiguity, pre-commit guidelines, change discipline, and decisionmaking authority.
Removed PR best practices link from the Sources Of Truth section as agents should not be making PRs
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.
Added comprehensive agent instructions covering scope, sources of truth, handling ambiguity, pre-commit guidelines, change discipline, and decisionmaking authority.
Based on the PyPDFForm AGENTS.md file.
What is this change?
Considerations for discussion
How to test the changes (if needed)
Breaking Changes
Breaking changes are changes to our public API which may require existing users to change their code. If there are no breaking changes, any existing parsons user should not need to do anything after updating their parsons version.
Does this PR introduce breaking changes?
Details (if needed)