-
Notifications
You must be signed in to change notification settings - Fork 14.5k
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
Approval permission for 1.32 Release #48158
Conversation
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
/approve |
Guessing you meant dev-1.32 there! |
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 PR seems to target the wrong branch.
/approve cancel
I assume that you meant to send this PR in against dev-1.32
No. I don't think this should target dev-1.32. The change to OWNER_ALIAS is temporary, but the whole site wide. I could be wrong though. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: tengqm The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Hey @sftim I followed the examples above and targeted the PR to the main branch, let me know if it is indeed the wrong branch, but if not, could I get your lgtm? |
I still think this is the wrong approach. I don't object to another person adding LGTM if other people are confident I'm wrong. |
OWNERS_ALIASES
Outdated
@@ -66,6 +66,7 @@ aliases: | |||
- tengqm | |||
- Princesso # RT 1.31 Docs Lead | |||
- drewhagen # RT 1.31 temp acting Docs lead |
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.
I think Princess and I were supposed to be removed. Could you do me a favor and remove us as well?
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.
Done!
drew and princess were docs leads for past release cycles, their membership in owners is not required anymore
This is correct. The PR needs to target the main branch as it has every release. |
LGTM label has been added. Git tree hash: 40913fe5dfba099a5e8b9c08f55582584df085eb
|
As the 1.32 Release Docs lead, I would like to add myself to the approver list for the dev-1.32 branch