Repository navigation
Conversation
Add a link to the GitHub Actions workflow run in the comments posted by the cherry-pick workflow, for both successful cherry-picks and conflict notifications. This helps contributors quickly access the workflow logs for debugging or verification. Fixes WordPress#76575
|
Warning: Type of PR label mismatch To merge this PR, it requires exactly 1 label indicating the type of PR. Other labels are optional and not being checked here.
Read more about Type labels in Gutenberg. Don't worry if you don't have the required permissions to add labels; the PR reviewer should be able to help with the task. |
|
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 If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
github-actions
Bot
added
the
First-time Contributor
|
👋 Thanks for your first Pull Request and for helping build the future of Gutenberg and WordPress, @jigangz! In case you missed it, we'd love to have you join us in our Slack community. If you want to learn more about WordPress development in general, check out the Core Handbook full of helpful information. |
|
Note: this is a reopen of #76577, which was closed unintentionally. I rebased to fix a git author email mismatch (commits were using a local auto-generated email instead of my GitHub-linked one), which accidentally broke the branch history. All changes are the same as the original PR. |
|
@desrosj Friendly ping — this PR has been open for about a week with CI passing. Would you have a chance to review when you get a moment? Thanks! |
What?
Add a link to the GitHub Actions workflow run in the comments posted by the
cherry-pick-wp-releaseworkflow.Why?
When the cherry-pick workflow comments on a PR (either for a successful cherry-pick or a conflict notification), there is no link back to the workflow run logs. This makes it harder for contributors to debug failures or verify the cherry-pick. See #76575.
How?
For each
actions/github-scriptstep that posts a PR comment, this PR:run_urlenvironment variable using${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}[Workflow run](${runUrl})link to the comment bodyThis applies to both the success comment ("Comment on the PR") and the conflict comment ("Comment on the PR about conflict") steps.
Testing Instructions
This change only affects workflow comment formatting. It can be verified by:
Fixes #76575