spring-projects / spring-projects/spring-security
Gradle Wrapper Bot should facilitate forward port issues
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 9.6k
- Forks
- 6.3k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 52
Description
When the Gradle Wrapper Bot creates a PR to update Gradle, it does it for only one branch. When forward porting to other branches, no forward port issues attached to the other affected versions are created. Thus, those forward port issues must be created manually.
There are at least two alternatives to creating the forward port issues manually:
- Configure the bot to create an upgrade PR for each branch. The downside here is that there is that it quadratically increases the amount of forward porting to be done
- Configure the bot to include the PR number in the commit, like
Closes PR-13456. In that case, the forward port bot will create the appropriate issues automatically while forward porting.
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 by tracing how the Gradle Wrapper Bot creates upgrade pull requests and how the forward port bot recognizes commit references across branches. Compare the two proposed approaches and confirm that the chosen implementation creates the appropriate forward port issues automatically without requiring manual creation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100