-
Notifications
You must be signed in to change notification settings - Fork 7.4k
[Chore] Rationalize GHA as part of 'how we docs' exercise #23761
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
Conversation
This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:
|
@@ -0,0 +1,21 @@ | |||
name: Issue - Label and assign | |||
|
|||
# **What it does**: Labels Issues with associated products. Updates assignees to match our CODEOWNERS file. |
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.
Re-creates issue.yml
, but with clearer naming
@@ -36,3 +39,16 @@ jobs: | |||
with: | |||
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} | |||
continue-on-error: true | |||
|
|||
assign: |
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.
This pulls in from the pr.yml
. These are triggered on the same event, so we should have them all running in the same action.
Preview URL: https://c8ed7e52.preview.developers.cloudflare.com |
Summary
As part of writing the
content reviews
section of How we docs, I got confused myself parsing through our GHA.This consolidates dupe actions and clarifies the file naming structure.
Risk
Small to no risk for this change. If this breaks, we lose labeling and assignment for a bit, which can be fixed easily and doesn't impact the team too drastically.