Skip to content

fix: add jira-user-email to Jira linter workflow #8050

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

Closed
buger wants to merge 1 commit into from
Closed

fix: add jira-user-email to Jira linter workflow #8050

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
2 changes: 1 addition & 1 deletion .github/workflows/jira-pr-validator.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,4 +24,4 @@
uses: TykTechnologies/jira-linter@38a9cabef56171c4e52ea698fa7be3db5fca3a49 # main
with:
jira-base-url: 'https://tyktech.atlassian.net'
jira-api-token: ${{ secrets.JIRA_TOKEN }}
jira-api-token: ${{ secrets.JIRA_TOKEN }}

Check failure on line 27 in .github/workflows/jira-pr-validator.yaml

View check run for this annotation

probelabs / Visor: architecture

logic Issue 

The change in the diff appears to be a no-op, replacing a line with an identical one. This contradicts the pull request title and description, which state that the `jira-user-email` input is being added to fix the Jira linter workflow. The commit does not implement the described change, and therefore the underlying issue will not be resolved.
Raw output 
Please amend the commit to correctly add the `jira-user-email` input to the `jira-linter` action's `with` block. The Atlassian API requires both email and token, so this parameter is necessary to fix the workflow as described in the pull request summary.

Check failure on line 27 in .github/workflows/jira-pr-validator.yaml

View check run for this annotation

probelabs / Visor: quality

logic Issue 

The code change shown in the diff appears to be a no-op, replacing a line with an identical one. This does not align with the PR's description, which states the goal is to add the `jira-user-email` input to fix a failing Jira integration. The intended fix seems to be missing from this pull request.
Raw output 
Update the pull request to include the necessary `jira-user-email` input for the `TykTechnologies/jira-linter` action. Based on the PR description, a line should be added for the user email, for example: `jira-user-email: ${{ secrets.JIRA_USER_EMAIL }}` (assuming that is the correct secret name).
Loading