Release PRs from release-please don't run CI
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 64/100
Research direction
Start by reading the GitHub Actions workflow that runs release-please and the CI workflow it should trigger. Check how the release PR is authenticated and compare that with the documented GitHub App token option. Done means a release PR runs the full CI check list and can satisfy required checks on main.
Written by the indexing model from the issue text.
Description
Problem
release-please opens its release PRs with the workflow's GITHUB_TOKEN. GitHub doesn't start other workflows for events caused by that token, so CI never runs on a release PR. That's why #3 had no checks.
Today this is harmless, because a release PR only changes the manifest and changelog. But if branch protection on main ever requires checks, release PRs can't be merged. And a release could be cut without CI having run on that exact commit, although the release workflow's build-python job does re-run the tests before publishing.
Options
- Use a GitHub App token (e.g.
actions/create-github-app-token) for release-please. PRs and pushes it makes do trigger CI. This is recommended. - Or a fine-grained PAT stored as a secret (less preferred: a long-lived credential).
Done when
- A release PR shows the full CI check list.
- Branch protection on
maincan require CI without blocking releases.
- Dominant language
- Python
- Stars
- 0
- Forks
- 0
- Avg merge
- 28m
- Merged PRs (30d)
- 20
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from bitpin-dev/bitpin-sdk
-
documentation java release
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
bitpin-dev/bitpin-sdk#32 ·
Maintainers usually reply within 1 day
-
docs help wanted i18n
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
bitpin-dev/bitpin-sdk#8 ·
Maintainers usually reply within 1 day
-
enhancement go java websocket
Difficulty 4/5 3-5 days Newbie friendliness 52/100
bitpin-dev/bitpin-sdk#33 ·
Maintainers usually reply within 1 day
-
enhancement java
Difficulty 3/5 1-2 days Newbie friendliness 70/100
bitpin-dev/bitpin-sdk#31 ·
Maintainers usually reply within 1 day
-
bug python security
Difficulty 4/5 3-5 days Newbie friendliness 55/100
bitpin-dev/bitpin-sdk#30 ·
Maintainers usually reply within 1 day
All issues in bitpin-dev/bitpin-sdk
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
btclib-org/btclib-node#2132 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
freelawproject/juriscraper#2367 · 2 comments ·
Maintainers usually reply within 1 day
-
infra tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 1/5 Under an hour Newbie friendliness 78/100
gke-labs/kube-agents#4190 ·
Maintainers usually reply within 1 day