Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .github/PULL_REQUEST_TEMPLATE.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@

## Jira Ticket

<!-- e.g. RHAIENG-123 -->
<!-- e.g. RHAIENG-123. Include the ticket ID so the PR appears as a linked pull request on the Jira issue. -->

## Testing

Expand Down
8 changes: 6 additions & 2 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -61,7 +61,7 @@ This repository enforces the [Conventional Commits](https://www.conventionalcomm

### Format

```
```text
<type>(optional scope): <description>

[optional body]
Expand Down Expand Up @@ -102,12 +102,16 @@ 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"
```

## 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, 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

Every pull request is automatically labeled when opened or updated:
Expand Down
Loading