[wp-meta] [Making WordPress.org] #8126: Deprecate creating WordPress/wordpress.org Issues
Making WordPress.org
noreply at wordpress.org
Mon Nov 10 00:53:03 UTC 2025
#8126: Deprecate creating WordPress/wordpress.org Issues
-----------------------------+-------------------------
Reporter: dd32 | Owner: (none)
Type: task (blessed) | Status: new
Priority: normal | Milestone:
Component: Version Control | Keywords: needs-patch
-----------------------------+-------------------------
The WordPress.org github repository currently has Issues enabled, this was
done as an experiment to aid in project management.
Unfortunately this now means we have two locations where tickets can be
filed, which makes it difficult to deduplicate reports and ensure that all
relevant issues are known by whomever is working on it.[[BR]]
This has also resulted in confusion by reporters, who create tickets in
both locations, or create a issue (as a copy of Trac) such that they can
submit a PR.
I'd like to turn off issues on
https://github.com/WordPress/wordpress.org/issues eventually. Or leave it
only for issues transferred from other GitHub repositories.
In order to do this, we should start by adding GitHub Issue and PR
templates which remind submitters to a) Include a Trac reference in their
PRs and b) To create a ticket here on meta.trac preferably (Unless they
don't have a WordPress.org account).
Even if we don't turn off issue creation, adding those templates will
benefit contributors.
Note: I am not suggesting that we cease accepting PRs.
https://github.com/WordPress/wordpress.org/pulls
--
Ticket URL: <https://meta.trac.wordpress.org/ticket/8126>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org
More information about the wp-meta
mailing list