Add secrets to release drafter #47
Merged
Conversation
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
Contributor
Author
|
Question: Why does the release drafter template action succeed while annotating an error? |
Contributor
|
Why we need the secrets here? |
Contributor
Author
I saw this: https://github.com/Staffbase/backstage-techdocs-action/actions/runs/18160924557 If there is a different way to fix the current failures, I am more than happy to adjust |
Contributor
|
I would do it like here: https://github.com/Staffbase/gha-workflows/blob/main/.github/workflows/release-drafter.yml |
michikrug
force-pushed
the
fix-release-drafter
branch
from
b49c740 to
bca124f
Compare
0x46616c6b
approved these changes
Nov 3, 2025
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Type of Change
Description
Add secrets to be used by the release drafter workflow.
It currently fails to run without.
Checklist