docs: add contribution guidance - #67
Merged
Merged
Conversation
This repo is public and told a would-be contributor nothing: no CONTRIBUTING.md, no contribution section in the README, and no org-level default to fall back on. The substance is the one rule that matters here. A demo prints claims about what was enforced, denied or verified, and a reader believes them, so the script must check the thing it claims and fail loudly when the check fails. We have shipped the opposite once already: demo-06 printed "gate released key: False" under a heading saying the opposite. That is now written down as the bar for a merge, along with exiting non-zero on a failed assertion so CI catches it, and adding any new demo to ci.yml so it actually runs. Claims in the file were checked against the repo: requirements.txt exists and is what the README installs, tests/ exists, and ci.yml runs eight demos. Also clears the OpenSSF Best Practices criteria for contribution information, which is what surfaced the gap. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01XbDBXDWWvMFa7c2jGgyq9t
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
1 participant
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.
This repository is public and told a would-be contributor nothing: no
CONTRIBUTING.md, no contribution section in the README, and no org-level default to fall back on.The substance is the one rule that actually matters here. A demo prints claims about what was enforced, denied or verified, and a reader believes them, so the script has to check the thing it claims and fail loudly when the check fails. We shipped the opposite once already: demo-06 printed
gate released key: Falseunder a heading saying the opposite. That is now written down as the bar for a merge, along with exiting non-zero on a failed assertion so CI catches it, and adding any new demo toci.ymlso it actually runs.Every claim in the file was checked against the repo rather than assumed:
requirements.txtexists and is what the README installs,tests/exists, andci.ymlruns eight demos.Found while registering the nine agentrust-io repos on bestpractices.dev. Six are already at a passing badge; this was the gap standing between demos and the same.
🤖 Generated with Claude Code
https://claude.ai/code/session_01XbDBXDWWvMFa7c2jGgyq9t