Making WordPress.org

Opened 19 months ago

Last modified 18 months ago

#6533 new defect (bug)

PR Bot: Auto-generate a props list from activity on GitHub PR/s

Reported by: peterwilsoncc's profile peterwilsoncc Owned by:
Milestone: Priority: normal
Component: Trac Keywords:
Cc:

Description

As a lot of WordPress-Develop contributions happen on GitHub these days, it would be handy if the prbot could maintain a list of usernames that ought to be included in props upon commit.

This would be particularly handy for activity that isn't cross-posted to trac such as some review activity.

To aid committers giving props, it would be helpful if the usernames could be converted to their wordpress.org counterparts if the two are linked. For example the github user jrfnl would be listed as jrf to ensure Juliette is propped correctly.

An alternative approach could be to check PRs as a post-commit hook and add any names that have been missed to the props content-type in make/core.

Change History (7)

#1 @jrf
19 months ago

💯

On that note - I also keep noticing that while "normal" comments on GH get cross-posted to Trac, PR reviews and review comments (and possibly replies) do not get cross-posted. This means that Trac always only has a partial conversation if a PR lives on GitHub (and makes it very easy to miss contributors).

#2 @dd32
19 months ago

In 12116:

API: Trac GitHub Integration: When we know the WordPress.org user whose comments we're syncing from GitHub, link to the WordPress.org user rather than the GitHub user.

See #6533.

#3 @dd32
19 months ago

Last edited 19 months ago by dd32 (previous) (diff)

#4 follow-up: @jrf
19 months ago

@dd32 That was fast 😁

#5 in reply to: ↑ 4 @dd32
19 months ago

Replying to jrf:

@dd32 That was fast 😁

Some things are faster to do than others.. like handling PR comments.. :)

This ticket was mentioned in Slack in #core-committers by david.baumwald. View the logs.


18 months ago

This ticket was mentioned in Slack in #meta by tellyworth. View the logs.


18 months ago

Note: See TracTickets for help on using tickets.