Comment on a PR when no Trac ticket is included

[desrosj]

When contributing to Core using a pull request on GitHub, a ​Trac ticket is required for the contribution to be considered.

Even though the pull request template notes this, it's easy to forget or overlook.

Adding a job in the Pull Request Comments workflow to add a reminder comment when a Trac ticket link is missing is an easy way to help avoid contributions being lost in the shuffle.

When contributing to Core using a pull request on GitHub, a ​Trac ticket is required for the contribution to be considered.

Even though the pull request template notes this, it's easy to forget or overlook.

Adding a job in the Pull Request Comments workflow to add a reminder comment when a Trac ticket link is missing is an easy way to help avoid contributions being lost in the shuffle.

Trac ticket: https://core.trac.wordpress.org/ticket/60129

Trac ticket:

Was thinking about this a bit more today. I think we should also attempt to check if a previous comment exists to avoid multiple comments for the same thing on a PR.

Thank you for the review @desrosj and @peterwilsoncc!

I'll make the requested changes in the next few days when I have some free time. Feel free to let me know if you have any further suggestions!

[devsahadat]

It's crucial to remember including a Trac ticket link when contributing to WordPress Core via a GitHub pull request. Despite the reminder in the template, oversight happens.
Implementing a job in the PR Comments workflow to prompt for a missing Trac ticket link could prevent contributions from slipping through. Additionally, considering @anamarijapapic's suggestion to avoid duplicate comments on PRs would streamline the process further.

[anamarijapapic]

@desrosj @peterwilsoncc @swissspidy Any updates on this?

[desrosj]

Hi @anamarijapapic! Thanks for working on this, and apologies it took so long to circle back to!

I think that this looks to be in a good state. Let's give it a try!

[desrosj]

In 58092:

Build/Test Tools: Remind contributors to include a Trac ticket link.

Contributing to WordPress using wordpress-develop on GitHub is a useful way collaborate, test, and review suggested changes to the code base. One of the required criteria, though, is including a link to a corresponding Trac ticket. This ensures the PR and associated activity is listed on the Trac ticket, which serves as the source of truth.

It’s easy to forget this and newer contributors aren’t always aware of this requirement. This adds a GitHub Actions job that will add a comment as a reminder when no Trac ticket is included.

Is the waiting really ended? Two thousand years.

Props anamarijapapic, peterwilsoncc.
Fixes #60129.

Merged in https://core.trac.wordpress.org/changeset/58092.

[ocean90]

Should the comment be deleted once the link has been added?

[desrosj]

@ocean90 That's probably a good idea to limit the number of bot comments on the PR.

Looks like there is an edited activity type for pull_request_target/pull_request that could be used for this.

[desrosj]

In 58120:

Build/Test Tools: Remove check-latest input for setup-node.

The check-latest setting is used to ensure the latest version of Node.js is always installed in GitHub Action workflows.

This input was added and turned on in [57212] when the minimum required version of Node.js was bumped to 20.10.0. Because GitHub Action runner image updates are deployed on a rolling basis over the course of several days, a version of Node.js that met this new requirement was not always present (especially on Windows runners). Using this input was a temporary fix to ensure stability for Core’s test workflows.

The check-latest input does have some side effects. Two examples are:

• An additional request is performed to check the latest version every time setup-node is used with this option enabled. More requests are made to download and install a newer version of Node.js when one is available.
• When new versions of Node.js are released, the Core workflows immediately switch to the new version, which could potentially have undiscovered bugs or regressions.

The latter has surfaced today due to a regression in Node.js 20.13.0 on Windows (see ​https://github.com/nodejs/node/issues/52884).

A bit of time has passed and a version >=20.10.0 is now reliably available on all GitHub Action runners. Running the very latest release Node.js is also not important for Core’s testing setup, so check-version can safely be removed to address both side effects detailed above.

Props johnbillion.
Fixes #60129.

[desrosj]

I don't have the availability to tackle the suggestion above between now and 6.6 final release, and this will only require changes to trunk anyway.

I've opened #61567 for the follow up suggestion, and I'm closing this out so the ticket and changes made during this cycle can remain there.