googleapis / googleapis/release-please-action
Release please tags non released commits
- Dominant language
- TypeScript
- Stars
- 2.5k
- Forks
- 327
- PR merge metrics
- No merged PRs in 30d
Description
Hello
I have an issue releasing with release please, my workflow is simple. On every commit to my main branch I run the pipeline that test the code and executes release please.
On PR merged I'm releasing and tagging the code using release please.
If I'm merging my PR during a main pipeline then the last commit on main that wasn't embarked in the PR, nor tested and not shown in the changelog is tagged within the release and then is kinda lost forever.
Do someone can help on this ?
Contributor guide
Research direction
Start by reproducing the reported workflow: run release please on every commit to main and again after merging a PR, then inspect which commit is tagged and listed in the changelog. A fix is complete when the release includes only tested, changelog-covered commits from the intended PR and does not silently tag an unrelated main-branch commit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- ci-cd, release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100