feat: pass triage_project_token to support-comment workflow#4
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Pass the new
triage_project_tokensecret to the sharedsupport-commentreusable workflow.spacelift-io/.githubis adding a step that places new issues/PRs on the Spacelift Triage Board. That step needs a cross-org token, exposed to the reusable workflow as thetriage_project_tokensecret. This PR wires it through from this repo.See spacelift-io/.github#1 for the reusable-workflow change.
Changes
.github/workflows/support-comment.yaml: passtriage_project_token: ${{ secrets.SUPPORT_TRIAGE_PROJECT_TOKEN }}alongside the existingslack_webhook_urlsecret.Requires the
SUPPORT_TRIAGE_PROJECT_TOKENsecret to be present (set as an org-level Actions secret).