Repository navigation
Route specification proposals through SpecDoc - #25
Merged
Merged
Conversation
Point contributors to the existing review flow and close submissions from outside the organization. Preserve publication and maintenance overrides for the netfyr bot and organization members, and reuse the routing explanation when a pull request is reopened. Keep the workflow scoped to the repository and include the Actions policy needed to allow its pull_request_target event. Signed-off-by: Josephine Pfeiffer <josie@redhat.com>
Point contribution guidance and the submission-policy comment at the current netfyr board so proposals use the deployment's current origin. Signed-off-by: Josephine Pfeiffer <josie@redhat.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
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.
Point outside contributors to SpecDoc and close specification submissions that bypass its review flow. Preserve publication and maintenance overrides for the bot and organization members, and avoid repeating the routing comment when a pull request is reopened.
The repository needs the scoped Actions policy for this workflow’s pull_request_target event before activation.