Should update History document of base branch instead of default branch
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 10
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
Currently, if Jekyllbot merges a backport pull request at jekyll/jekyll onto 4.2-stable branch, it updates the HISTORY.markdown at master instead of the counterpart at base branch 4.2-stable.
Contributor guide
No contributing guide indexed for this repository
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
Trace the backport pull request merge handling and the code that updates HISTORY.markdown. Reproduce or inspect a merge onto 4.2-stable, then verify that the history update targets 4.2-stable rather than master.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- release
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100