Skip to content
Merged
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
30 changes: 30 additions & 0 deletions .github/pull_request_template.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,30 @@
<!--
Use a Conventional Commit PR title: <type>(<optional scope>): <description>

Examples:
feat(incidents): add incident filtering [IR-1234]
fix(alerts): handle missing alert details [IR-1234]
docs: clarify CLI configuration
chore(deps): update dependencies

Use feat for new features, fix for bug fixes, and ! before the colon for
breaking changes, e.g. feat!: remove a deprecated command.

Release Please uses commit messages for release notes and version bumps.
When squash-merging, ensure the final commit title follows this format too.
Keep relevant Linear issue IDs as a title suffix, as shown above, and link
the ticket in the description. The title must start with the Conventional
Commit type, not the ticket ID (e.g. avoid [IR-1234] feat(...): ...).
-->

## Description

<!-- What changes are being made, and why? Link any relevant Linear issues. -->

## Testing

<!-- Describe how the changes were verified, or explain why tests are not needed. -->

## Risk Assessment

<!-- Describe any risks, breaking changes, or migration steps. -->
Loading