-
Notifications
You must be signed in to change notification settings - Fork 3.2k
Testing workflow permissions #9901
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 workflow should only ever run in `trunk`.
…workflows. These permissions are not required for a public repo but are required for a private repo, for example a private fork. Props johnbillion, desrosj See #63170 git-svn-id: https://develop.svn.wordpress.org/trunk@60612 602fd350-edb4-49c9-b593-d223f7449a82
…Actions workflows. These permissions are not required for a public repo but are required for a private repo, for example a private fork. Props johnbillion, desrosj Follow-up to r60612. See #63170 git-svn-id: https://develop.svn.wordpress.org/trunk@60624 602fd350-edb4-49c9-b593-d223f7449a82
Test using WordPress PlaygroundThe changes in this pull request can previewed and tested using a WordPress Playground instance. WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser. Some things to be aware of
For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation. |
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the Core Committers: Use this line as a base for the props when committing in SVN: To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
|
Merged in r60773. |
It looks like r60612 and r60624 will need to be backported to older branches.
When working on a ticket that backported changes to older branches, I noticed that the Check Built Files workflow was failing for the 6.8 branch with the following error:
The same was true with the upgrade develop testing workflow:
All of the others seem to be working as expected. These two workflows were introduced during the 6.8 cycle, so thankfully this does not need to be backported further. @johnbillion I'm going to add this to the list we have started for a GitHub Actions page in the handbook.
Trac ticket: Core-63170
This Pull Request is for code review only. Please keep all other discussion in the Trac ticket. Do not merge this Pull Request. See GitHub Pull Requests for Code Review in the Core Handbook for more details.