WordPress / WordPress/grunt-patch-wordpress
List PRs along with patches when `grunt patch:<ticket###>
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 51
- Forks
- 13
- PR merge metrics
- No merged PRs in 30d
Description
Now that meta#4093 has updated the Core Trac to introduce a Pull Requests integration from Github;
When using grunt patch on a ticket number or url it would be nice to have it include the associated PRs.
As the feature becomes used more people will start to mingle a mix of the two. If grunt patch listed both in order then we'd avoid overlooking which actually is more recent the patch or PR... and some people may even overlook the PR if they're not used to them.
Originated from this core-comment I made;
https://meta.trac.wordpress.org/ticket/4903#comment:30
Thank you
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the grunt patch command entry point and trace how patches are retrieved for a ticket number or URL. Determine how associated GitHub pull requests can be obtained and ordered with patches; done means the command lists both kinds of changes in recency order without overlooking either.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, javascript
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100