[wp-meta] [Making WordPress.org] #4447: Create an easier way to track contributions across GitHub and Trac (was: Create an easier way to trac contributions across GitHub and Trac)

Making WordPress.org noreply at wordpress.org
Tue Feb 1 03:03:57 UTC 2022

#4447: Create an easier way to track contributions across GitHub and Trac
 Reporter:  desrosj      |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:
Component:  Profiles     |  Resolution:
 Keywords:               |

Comment (by desrosj):

 It's been ~3 years since discussion about solving the problem has taken
 place, and this is still an issue with every release. I've published a
 proposal on the Making WordPress Core blog with a suggestion to add a line
 to merge commit messages where the merging contributor compiles a list of
 props manually: https://make.wordpress.org/core/2022/01/31/ensuring-

 I'm also halfway through a GitHub Action that will get:
 - A list of all contributors that have commented on the current PR and all
 issues attached.
 - A list of all contributors that have engaged in review related
 discussion on the current PR.
 - A list of all contributors that made commits to the current PR's branch.
 - A list of all contributors that have commented on linked tickets (either
 manually, or with [https://docs.github.com/en/issues/tracking-your-work-
 with-issues/linking-a-pull-request-to-an-issue GitHub's keyword linking]).

 The idea is that these lists will be posted in a comment on the PR, and it
 will be updated periodically to contain the most up to date contributor
 lists, similar to how the `github-actions`
 user updates the comment with performance details for the PR].

 This should alleviate some of the burden on the Gutenberg maintainers when
 it comes time to merge a pull request, but the list should still be
 manually reviewed to filter out anyone that did not actually contribute.

 The idea is that the current w.org props script that parses a git log for
 `wordpress-develop` can be adjusted to also consume the git log for
 `gutenberg`, and using the behind the linked GH profile feature added
 above, the GH usernames can be replaced with w.org ones, and the props
 more accurately calculated (and less manually).

Ticket URL: <https://meta.trac.wordpress.org/ticket/4447#comment:25>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

More information about the wp-meta mailing list