-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: Callout outside contributors process #1969
Conversation
Refactor the caveat about outside contributors to have a linkable heading.
I'm looking at this PR where it looks like a forked branch is having its checks run. Is that supposed to be happening? |
@Igarfinkle |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure if this PR is still draft or not, but the verbiage looks good to me.
## [3.1.0](3.0.2...3.1.0) (2022-07-13) ### Features * Remove example app ([#2162](#2162)) ([1eb579e](1eb579e)) * USWDS 2.13.3 ([#2175](#2175)) ([fdeefc6](fdeefc6)) ### Bug Fixes * Danger contributors check ([#2167](#2167)) ([c05fe06](c05fe06)) * Emit headingLevel type and do not emit type declarations for tests ([#2134](#2134)) ([a4501dd](a4501dd)) * export SummaryBoxHeading and SummaryBoxContent ([#2100](#2100)) ([141ba8e](141ba8e)) ### Documentation & Examples * Callout outside contributors process ([#1969](#1969)) ([7881191](7881191)) * Update releasing docs ([#2018](#2018)) ([6849dda](6849dda))
Summary
Outside contributors can submit PRs against but can't have our status checks run on their forked branches due to security concerns. We mitigate these limitations by having documentation around outside contributions. This patch series helps by adding documentation and messaging to outside contributors so that both maintainers and contributors know what next steps are. We can continue fleshing this out going forward as well.
Related Issues or PRs