-
Notifications
You must be signed in to change notification settings - Fork 10
feat: adding bot configuration to docs #53
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
Merged
cjdcordeiro
merged 2 commits into
canonical:main
from
asanvaq:ROCKS-2779-add-a-sync-bot
Jan 15, 2026
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,59 @@ | ||
| settings: | ||
| # Jira project key to create the issue in | ||
| jira_project_key: "ROCKS" | ||
|
|
||
| # Dictionary mapping GitHub issue status to Jira issue status | ||
| status_mapping: | ||
| opened: Untriaged | ||
| closed: done | ||
| # (Optional) Use different status for GitHub issues closed as not planned (instead of closed as | ||
| # completed) | ||
| # https://github.blog/changelog/2022-03-10-the-new-github-issues-march-10th-update/#%F0%9F%95%B5%F0%9F%8F%BD%E2%99%80%EF%B8%8F-issue-closed-reasons | ||
| # If not specified, `closed` status will be used. | ||
| not_planned: rejected | ||
|
|
||
| # (Optional) Jira project components that should be attached to the created issue | ||
| # Component names are case-sensitive | ||
| components: | ||
|
|
||
| # (Optional) GitHub labels. Only issues with one of those labels will be synchronized. | ||
| # If not specified, all issues will be synchronized | ||
| labels: | ||
|
|
||
| # (Optional) (Default: false) Add a new comment in GitHub with a link to Jira created issue | ||
| add_gh_comment: false | ||
|
|
||
| # (Optional) (Default: false) Add a 'synced-to-jira' label to newly created issues once a | ||
| # corresponding ticket is successfully created in Jira. | ||
| # This label serves as confirmation that the issue sync process was completed successfully. | ||
| add_gh_synced_label: false | ||
|
|
||
| # (Optional) (Default: true) Synchronize issue description from GitHub to Jira | ||
| sync_description: true | ||
|
|
||
| # (Optional) (Default: true) Synchronize comments from GitHub to Jira | ||
| sync_comments: true | ||
|
|
||
| # (Optional) (Default: None) Parent Epic key to link the issue to | ||
| epic_key: "ROCKS-2724" | ||
|
|
||
| # (Optional) Dictionary mapping GitHub issue labels to Jira issue types. | ||
| # If label on the issue is not in specified list, this issue will be created as a Bug | ||
| label_mapping: | ||
| enhancement: Task | ||
|
|
||
| # (Optional) JIRA issue's summary | ||
| # This field can be used to customize the JIRA issue's summary (title). | ||
| # The value of the field will be passed to the python | ||
| # format() method to generate the JIRA summary. The GH issue | ||
| # variable will be captured in the format() method so that users can | ||
| # use GH issue attribute's values to build the JIRA summary. | ||
| # See GH issue definition : | ||
| # https://docs.github.com/en/rest/issues/issues?apiVersion=2022-11-28 | ||
| # | ||
| # Examples: | ||
| # to use fixed title "github issue": "github issue" | ||
| # to use GH issue title: "{issue.title}" | ||
| # to add prefix "[GitHub]" : "[GitHub] {issue.title}" | ||
| # to add user in the title (between square brackets): "[{issue.user.login}] {issue.title}" | ||
| summary: "[GitHub] {issue.title}" | ||
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.
Uh oh!
There was an error while loading. Please reload this page.