docs: add absolute ublue-os write prohibition to org AGENTS.md#6
Merged
Conversation
Strengthens the ublue-os policy from "don't send PRs" to an absolute prohibition matching the local AGENTS.md language: no issues, PRs, comments, forks, webhooks, automated reports, or any programmatic write action to ublue-os/* repos. Violating this risks the projectbluefin org being banned from GitHub. Assisted-by: Claude Sonnet 4.6 via GitHub Copilot Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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.
Problem
The org-level AGENTS.md only says "Do NOT send a PR to these projects" for ublue-os repos. This is much weaker than the absolute prohibition in
projectbluefin/common's local AGENTS.md, which bans all programmatic writes (issues, PRs, comments, forks, webhooks, automated reports).An agent bootstrapping cold from the org-level document may correctly infer that filing issues against ublue-os repos is permitted — and violating this risks getting the projectbluefin org banned from GitHub.
Changes
🚫 Absolute prohibition — ublue-os orgsection before the Consuming repos list, matching the language inprojectbluefin/common/AGENTS.mdWhy now
Caught during an architectural review of the factory pipeline automation gaps in
projectbluefin/common.Assisted-by: Claude Sonnet 4.6 via GitHub Copilot
Co-authored-by: Copilot 223556219+Copilot@users.noreply.github.com