From 0b1b2068eb3886827c4fc499ae7e84234457c1d8 Mon Sep 17 00:00:00 2001 From: Tarun Kumar Reddy Etikala Date: Sun, 3 May 2026 22:20:23 -0400 Subject: [PATCH 1/3] docs: document Jira + GitHub PR linking integration Add guidance on how Jira ticket IDs in PR titles, branch names, or the PR template field auto-link pull requests to Jira issues. Co-Authored-By: Claude Opus 4.6 (1M context) --- .github/PULL_REQUEST_TEMPLATE.md | 2 +- CONTRIBUTING.md | 4 ++++ 2 files changed, 5 insertions(+), 1 deletion(-) diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md index b52227d7..19c90d95 100644 --- a/.github/PULL_REQUEST_TEMPLATE.md +++ b/.github/PULL_REQUEST_TEMPLATE.md @@ -4,7 +4,7 @@ ## Jira Ticket - + ## Testing diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 7c53bca4..05a5e54e 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -108,6 +108,10 @@ feat: change /chat response format BREAKING CHANGE: response field "text" renamed to "content" ``` +## Linking PRs to Jira + +This repository has GitHub + Jira integration enabled. When you include a Jira ticket ID (e.g. `RHAIENG-123`) in your PR title, branch name, or the **Jira Ticket** field in the PR template, the pull request automatically appears under **Development** on the Jira issue. This gives the visibility into which tickets have active or merged code without leaving Jira. + ## Automated PR labels Every pull request is automatically labeled when opened or updated: From e6e2cc4dd3d39333b61765f3c1de6386bd9f6853 Mon Sep 17 00:00:00 2001 From: Tarun Kumar Reddy Etikala Date: Mon, 4 May 2026 11:07:52 -0400 Subject: [PATCH 2/3] docs: add language tags to fenced code blocks in CONTRIBUTING.md Fixes markdownlint MD040 violations on two code blocks missing language identifiers (commit message format template and breaking change example). Co-Authored-By: Claude Opus 4.6 (1M context) --- CONTRIBUTING.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 05a5e54e..2987d369 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -61,7 +61,7 @@ This repository enforces the [Conventional Commits](https://www.conventionalcomm ### Format -``` +```text (optional scope): [optional body] @@ -102,7 +102,7 @@ feat!: change /chat response format For breaking changes, add `!` after the type/scope (e.g. `feat!:`) or include a `BREAKING CHANGE:` footer: -``` +```text feat: change /chat response format BREAKING CHANGE: response field "text" renamed to "content" From 5ea95869fe918e594a0212beabf235828b965924 Mon Sep 17 00:00:00 2001 From: Tarun Kumar Reddy Etikala Date: Mon, 4 May 2026 15:28:45 -0400 Subject: [PATCH 3/3] docs: address PR review feedback on Jira linking section MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Add commit messages to the list of places Jira scans, use "PR description" instead of "Jira Ticket field in the PR template", and fix grammar ("the visibility" → "visibility"). Co-Authored-By: Claude Opus 4.6 (1M context) --- CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 2987d369..31392af8 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -110,7 +110,7 @@ BREAKING CHANGE: response field "text" renamed to "content" ## Linking PRs to Jira -This repository has GitHub + Jira integration enabled. When you include a Jira ticket ID (e.g. `RHAIENG-123`) in your PR title, branch name, or the **Jira Ticket** field in the PR template, the pull request automatically appears under **Development** on the Jira issue. This gives the visibility into which tickets have active or merged code without leaving Jira. +This repository has GitHub + Jira integration enabled. When you include a Jira ticket ID (e.g. `RHAIENG-123`) in your PR title, branch name, commit message, or PR description, the pull request automatically appears under **Development** on the Jira issue. This gives visibility into which tickets have active or merged code without leaving Jira. ## Automated PR labels