0a11d03ce5
Remove milestone from unmerged PRs ( #41216 )
...
* Remove milestone from unmerged PRs
* Add pr write permission to milestone manager
2023-11-03 13:22:07 -05:00
a07f35c384
Revert "Branch to test sadow pr 41200"
2023-11-03 11:40:55 +00:00
023887c02e
Remove milestone from unmerged PRs
2023-11-02 16:07:46 -05:00
eb210907e0
Update workflow to not add label when PR has already been analyzed ( #39545 )
2023-08-03 08:35:51 -05:00
bfedd049c1
Abstract PR scrub action so it can be used in two places ( #39329 )
...
* Abstract PR scrub action so it can be used in two places
* Rename composite action; add newline
2023-07-20 14:09:46 -05:00
2f407cb172
Update post-merge workflow to add 'needs: analysis' label ( #39277 )
2023-07-17 17:01:36 -05:00
1b74871bae
Assign milestone only if a PR touches WooCommerce Core ( #36897 )
...
* Assign milestone only if a PR touches WooCommerce Core
* add woocommerce-admin to list of paths
2023-02-21 18:21:29 +01:00
341541964c
Update action dependencies to remove set-output and save-state warnings ( #36549 )
2023-01-27 20:26:54 +13:00
16386238cc
Add minimum required permissions for workflow token ( #36200 )
...
* Add minimum required permissions to e2e-tests
* Add minimum token permission to more workflows
2023-01-02 09:28:11 -08:00
254fbd994f
Remove post merge comment about adding testing instructions ( #35498 )
2022-11-04 11:39:13 -07:00
18901f19a7
Remove the check for plugins: woocommerce label ( #34820 )
2022-09-23 12:11:50 -07:00
57c1c0bc1c
Freeze Ubuntu release to 20.04 for best practice and consistency
2022-04-26 18:28:56 -07:00
f08f58e241
Add additional checks for a label and targetting trunk
2022-03-31 06:41:18 -07:00
91442cd5d1
Limited Post-Merge Comment
...
Since this is for the WooCommerce release process,
we should only trigger it for the Core plugin.
2022-02-22 10:04:33 -08:00
6fb769bc9d
Refactor the PR post-merge processing GitHub action
...
Common code has been extracted to a "post-request-shared.php" script.
2021-08-03 11:33:33 +02:00
b3617a3115
Extend post-merge GH action to add a comment suggestion next steps.
2021-08-03 10:07:24 +02:00
9ffddbac1f
Use 'pull_request_target' in the automatic milestoning action
...
The original event used, 'pull_request', runs in the context of the
pull request. In the case of pull requests created from forks this means
that a read-only GitHub token is used for API calls, and thus the
call used to assign the milestone fails.
The fix is using the 'pull_request_target' event, which runs in the
context of the base branch, and thus with a read-write token. See:
https://docs.github.com/en/actions/reference/events-that-trigger-workflows#pull_request_target
Also, added a warning message when no milestone without a release
branch is found and thus the newest existing milestone is assigned
(this is a fallback that should normally not happen).
2021-07-29 16:47:27 +02:00
5da39b4ff0
Enclose action step name in double quotes for consistency.
...
Co-authored-by: Leif Singer <git@singer.sh>
2021-04-16 15:48:38 +02:00
a0c965964b
Add a GitHub action for automatic assignment of milestone to merged PRs
...
The milestone is chosen as follows:
1. List all the open milestones with a title of "X.Y.Z"
2. Sort them desc using verson_compare
3. foreach them in order, and take the last one not having a
corresponding release branch ("release/X.Y")
2021-04-15 17:16:00 +02:00
jonathansadowski
nigeljamesstevenson
Jonathan Sadowski
Leif Singer
Sam Seay
Roy Ho
Christopher Allford
Nestor Soriano
Néstor Soriano