ci: release candidate pull request doesn't have a reference to main branch
Open
Beginner friendly
Nobody has claimed this yet.
bug
build
release
- Dominant language
- Go
- Stars
- 305
- Forks
- 46
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 23
Description
🔭 Odd happeneings found in release testing but no blocker immediate!
[ ] Confirm unit tests and E2E tests are passing on the branch.
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 .github/workflows/release.yml around line 117 and inspect the release candidate pull request referenced in the issue, PR 579. Check how the workflow identifies the branch and how the release candidate is expected to reference main; done means the generated pull request includes that reference while the unit and E2E test checks remain passing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, go
- Domain
- ci-cd, release
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100