chore: fix release workflow dispatch repo resolution#2057
Merged
zeitlinger merged 1 commit intomainfrom Apr 27, 2026
Merged
Conversation
Signed-off-by: Gregor Zeitlinger <gregor.zeitlinger@grafana.com>
martincostello
approved these changes
Apr 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Pass
--repo "${GITHUB_REPOSITORY}"to thegh workflow run release.ymlcall inrelease-please.yml.Why
The
Release Pleaseworkflow dispatch step runs without a checkout, soghcannot infer the repository from.git. The failed run forv1.6.0stopped withfatal: not a git repositorybeforerelease.ymlwas dispatched.Impact
This allows the existing release workflow to be triggered from the
Release Pleasejob without adding an unnecessary checkout step.Validation
73146303246and confirmed the dispatch step was the failure point.--repoexplicitly when dispatching workflows from Actions.mise run lintlocally.Follow-up
After this lands,
release.ymlcan be manually dispatched withtag=v1.6.0to publish the existing tag.