Skip to content

Require approval for upstream feedback#5

Merged
shinaoka merged 6 commits into
mainfrom
agent/upstream-feedback-permissions
Jul 24, 2026
Merged

Require approval for upstream feedback#5
shinaoka merged 6 commits into
mainfrom
agent/upstream-feedback-permissions

Conversation

@shinaoka

Copy link
Copy Markdown
Member

Summary

  • recommend reporting likely bugs found in referenced, consulted, or ported-from upstream libraries
  • require explicit permission before drafting an upstream issue or PR patch
  • require separate explicit permission before external submission
  • advertise the policy in the shared rules index

Why

Upstream feedback is valuable, but both preparation of upstream-facing material and external publication should remain under explicit user control. Draft permission must not be interpreted as submission permission.

Validation

  • focused policy assertion covering the two approval gates and non-authorization clause
  • rules/index.md link validation (10 links)
  • git diff --check

@shinaoka
shinaoka merged commit b1a6fcc into main Jul 24, 2026
1 check passed
@shinaoka
shinaoka deleted the agent/upstream-feedback-permissions branch July 24, 2026 07:16
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