Skip to content

fix: pass the jira-username as a secret (CORE-1490) #32

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 27, 2024
Merged

fix: pass the jira-username as a secret (CORE-1490) #32

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 4 additions & 5 deletions .github/workflows/tag-tickets-with-release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,14 +19,13 @@ on:
type: boolean
required: false
default: false
jira-username:
description: "The JIRA username to tag the release."
type: string
required: true
secrets:
llm-api-token:
description: "A valid LLM API token to be used by the action."
required: true
jira-username:
description: "The JIRA username to tag the release."
required: true
jira-api-token:
description: "A valid JIRA API token to be used by the action."
required: true
Expand Down Expand Up @@ -65,7 +64,7 @@ jobs:
description: ${{ steps.llm_action.outputs.response }}
target-branch: ${{ inputs.target-branch }}
jira-token: ${{ secrets.jira-api-token }}
jira-email: ${{ inputs.jira-username }}
jira-email: ${{ secrets.jira-username }}
jira-domain: ${{ inputs.jira-domain }}
dry-run: ${{ inputs.dry-run }}
is-release: ${{ inputs.is-release }}