Skip to content
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.

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

ORCH-500 Add Jira integration #212

Merged
merged 1 commit into from
Dec 24, 2024
Merged

ORCH-500 Add Jira integration #212

merged 1 commit into from
Dec 24, 2024

Conversation

pavel-mikula-sonarsource
Copy link
Contributor

@pavel-mikula-sonarsource pavel-mikula-sonarsource commented Dec 4, 2024

ORCH-500

How to review:

The new YML are replacing the old synchronize-jira.yml (if present)

Make sure the files in the PR are the same as these
PullRequestClosed.yml
PullRequestCreated.yml
RequestReview.yml
SubmitReview.yml

⚠️ Please make sure that PullRequestCreated.yml has the correct Jira project on the last line!

PULL_REQUEST_TEMPLATE is expected to be in .github/ folder and have this fragment:

Part of 
<!-- 
  Only for standalone PRs without Jira issue in the PR title: 
    * Replace this comment with Epic ID to create a new Task in Jira
    * Replace this comment with Issue ID to create a new Sub-Task in Jira
    * Ignore or delete this note to create a new Task in Jira without a parent 
-->

This should not touch any other file.


Please be aware that we are not actively looking for feature contributions. The truth is that it's extremely difficult for someone outside SonarSource to comply with our roadmap and expectations. Therefore, we typically only accept minor cosmetic changes and typo fixes. If you would like to see a new feature, please create a new thread in the forum "Suggest new features".

With that in mind, if you would like to submit a code contribution, make sure that you adhere to the following guidelines and all tests are passing:

  • Please explain your motives to contribute this change: what problem you are trying to fix, what improvement you are trying to make
  • Use the following formatting style: SonarSource/sonar-developer-toolset
  • Provide a unit test for any code you changed
  • If there is a JIRA ticket available, please make your commits and pull request start with the ticket ID (ORCH-XXXX)

We will try to give you feedback on your contribution as quickly as possible.

Thank You!
The SonarSource Team

@hashicorp-vault-sonar-prod hashicorp-vault-sonar-prod bot changed the title Add Jira integration ORCH-500 Add Jira integration Dec 4, 2024
Copy link

sonarqube-next bot commented Dec 4, 2024

Quality Gate passed Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube

Copy link

@davividal davividal left a comment

Choose a reason for hiding this comment

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

LGTM!

@davividal davividal merged commit 71912a4 into master Dec 24, 2024
8 checks passed
@davividal davividal deleted the Pavel/Automation branch December 24, 2024 12:53
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