Repository navigation
Five for the Future: wire the Test team into the contributor directory - #656
huzaifaalmesbah wants to merge 1 commit into
Conversation
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. Core Committers: Use this line as a base for the props when committing in SVN: To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. Props Bot commandsYou can trigger Props Bot actions by commenting on this PR:
|
There was a problem hiding this comment.
Pull request overview
Note
Copilot was unable to run its full agentic suite in this review.
Adds support for a new “test” contributor team in the contribution metrics wiring.
Changes:
- Added
testto the list of teams considered to have contribution-tracking data. - Mapped the
testteam slug to a GitHub repo (WordPress/test-handbook) for metrics sourcing.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| * 3. Add the team's post_name slug to this list. | ||
| */ | ||
| const TEAMS_WITH_DATA = array( 'core', 'meta' ); | ||
| const TEAMS_WITH_DATA = array( 'core', 'meta', 'test' ); |
| $map = array( | ||
| 'core' => array( 'WordPress/wordpress-develop', 'WordPress/gutenberg' ), | ||
| 'meta' => array( 'WordPress/wporg-main', 'WordPress/wporg-mu-plugins' ), | ||
| 'test' => array( 'WordPress/test-handbook' ), | ||
| ); |
Adds 'test' to TEAMS_WITH_DATA and maps it to WordPress/test-handbook in team_to_github_repos(), so /pledges/ on the Test make site renders the directory instead of the bring-tracking-to-this-team guide.
03a8890 to
6ceb81a
Compare
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Merge Risk: ⚪ Minimal · up to
|
| Check name | Status | Explanation |
|---|---|---|
| Description Check |  |
Check skipped - CodeRabbit’s high-level summary is enabled. |
| Title check | |
The title clearly describes the main change: wiring the Test team into the contributor directory. It is specific and consistent with the changeset and objectives. |
| Docstring Coverage | |
Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 1 functions across 1 files. |
| Linked Issues check | |
Check skipped because no linked issues were found for this pull request. |
| Out of Scope Changes check | |
Check skipped because no linked issues were found for this pull request. |
✨ Finishing Touches
-
🧪 Generate unit tests (beta)
-
- Create a new PR
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
Comment @coderabbitai help to get the list of available commands.
Adds
testtoTEAMS_WITH_DATAso/pledges/on the Test make site renders the directory instead of thebring-tracking-to-this-team guide.
Maps
testtoWordPress/test-handbookinteam_to_github_repos()so GitHub activity is scoped to the team's repo.No Trac mapping — the Test team has no Trac source, so the Trac branch in
get_team_contribution_metrics()is skipped and rankings come entirely fromwporg_github_activity.Summary by CodeRabbit