GHA-203 Do not use Jira tickets in integration PRs for draft releases#108
Merged
tomasz-tylenda-sonarsource merged 7 commits intomasterfrom Mar 4, 2026
Merged
GHA-203 Do not use Jira tickets in integration PRs for draft releases#108tomasz-tylenda-sonarsource merged 7 commits intomasterfrom
tomasz-tylenda-sonarsource merged 7 commits intomasterfrom
Conversation
SonarQube reviewer guide
|
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.




Draft releases use sandbox Jira tickets. When a PR is opened in SQC and SQS, these are assumed to be prod Jira tickets and automation incrrectly updates prod ticket.
Tested: https://github.com/SonarSource/sonar-apex/actions/runs/22669129730 (see the PRs)
Due to reference to
@v1in.github/workflows/automated-release.ymlthis will not work onmaster