Skip to content

Clarify fork-based contributor workflow#3

Closed
Parshan-MHB wants to merge 1 commit into
mainfrom
docs/fork-contributor-policy
Closed

Clarify fork-based contributor workflow#3
Parshan-MHB wants to merge 1 commit into
mainfrom
docs/fork-contributor-policy

Conversation

@Parshan-MHB
Copy link
Copy Markdown
Owner

Summary:
Clarify that external contributors should use forks while maintainers use feature branches in the main repository.

What Changed:

  • add an explicit access model section to CONTRIBUTING.md
  • explain the practical GitHub enforcement boundary for forks versus maintainer branches
  • keep the written workflow aligned with the current protected main policy

Verification:

  • reviewed CONTRIBUTING.md against the current repository permissions and branch protection model

Security Impact:
Repository governance only. No runtime behavior change.

Screenshots:
N/A

@Parshan-MHB Parshan-MHB enabled auto-merge (squash) April 21, 2026 12:20
@Parshan-MHB
Copy link
Copy Markdown
Owner Author

Superseded by #4, which recreates this change from current main and hardens the CI workflow to use an isolated scratch path with a bounded timeout.

auto-merge was automatically disabled April 21, 2026 12:31

Pull request was closed

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