SONARJAVA-6155 Use shared update rule metadata worflow#5488
SONARJAVA-6155 Use shared update rule metadata worflow#5488tomasz-tylenda-sonarsource wants to merge 1 commit intomasterfrom
Conversation
hashicorp-vault-sonar-prod
bot
changed the title
tomasz-tylenda-sonarsource
force-pushed
the
tt/update-rule-metadata-shared-worflow
branch
4 times, most recently
from
213046f to
06cdf91
Compare
tomasz-tylenda-sonarsource
requested a review
from aurelien-coet-sonarsource
tomasz-tylenda-sonarsource
force-pushed
the
tt/update-rule-metadata-shared-worflow
branch
from
06cdf91 to
70463df
Compare
| URL=$(gh pr create -B master --title 'Update rule metadata' --body '') | ||
| echo "url=${URL}" >> $GITHUB_OUTPUT | ||
| labels: '' | ||
| rspec-token-suffix: 'rspec' |
There was a problem hiding this comment.
Question: Why do we need a different suffix than 'rspec-read' ?
There was a problem hiding this comment.
We configured it independently from automated release, first for sonar-java (http://github.com/SonarSource/re-terraform-aws-vault/commit/367f3a9a0f22d0c6b0cf59969cf03f59a1a423f0), then for the other repos (http://github.com/SonarSource/re-terraform-aws-vault/commit/f11b3c03e9c82c0cfd6a9ab94f58b802d1da51ba). In fact, there is a mix or rspec and rspec-read (http://github.com/search?q=repo%3ASonarSource%2Fre-terraform-aws-vault%20%22suffix%3A%20rspec%22&type=code) and security folks are considering migrating to just "rspec".
|
2 participants
We will benefit from: