Skip to content

GHA-203 Do not use Jira tickets in integration PRs for draft releases#108

Merged
tomasz-tylenda-sonarsource merged 7 commits intomasterfrom
tt/dry-run
Mar 4, 2026
Merged

GHA-203 Do not use Jira tickets in integration PRs for draft releases#108
tomasz-tylenda-sonarsource merged 7 commits intomasterfrom
tt/dry-run

Conversation

@tomasz-tylenda-sonarsource
Copy link
Contributor

@tomasz-tylenda-sonarsource tomasz-tylenda-sonarsource commented Mar 4, 2026

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 @v1 in .github/workflows/automated-release.yml this will not work on master

@hashicorp-vault-sonar-prod hashicorp-vault-sonar-prod bot changed the title Do not use ticket in integration PRs for draft releases GHA-203 Do not use ticket in integration PRs for draft releases Mar 4, 2026
@tomasz-tylenda-sonarsource tomasz-tylenda-sonarsource changed the title GHA-203 Do not use ticket in integration PRs for draft releases Do not use Jira tickets in integration PRs for draft releases Mar 4, 2026
@hashicorp-vault-sonar-prod
Copy link

hashicorp-vault-sonar-prod bot commented Mar 4, 2026

GHA-203

@tomasz-tylenda-sonarsource tomasz-tylenda-sonarsource changed the title Do not use Jira tickets in integration PRs for draft releases GHA-203 Do not use Jira tickets in integration PRs for draft releases Mar 4, 2026
@sonarqubecloud
Copy link

sonarqubecloud bot commented Mar 4, 2026

Copy link
Contributor

@nils-werner-sonarsource nils-werner-sonarsource left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@tomasz-tylenda-sonarsource tomasz-tylenda-sonarsource merged commit 46301a1 into master Mar 4, 2026
7 checks passed
@tomasz-tylenda-sonarsource tomasz-tylenda-sonarsource deleted the tt/dry-run branch March 4, 2026 12:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants