Files
slsDetectorPackage/.github/pull_request_template.md
T
maliakal_d 147199eca5
Build on RHEL9 / build (push) Failing after 3m3s
Build on RHEL8 / build (push) Failing after 4m43s
pr template - release notes (#1565)
* removed no release note checkbox or theat No release note label added etc

* minor
2026-09-21 11:29:02 +02:00

147 lines
3.2 KiB
Markdown

<!--
Please complete all relevant sections. If not, validation could fail.
The expandable sections are guidance only — do not modify or fill them out.
-->
<details>
<summary>Help</summary>
The following are managed automatically by workflow. Do not set them manually.
- Labels: Feature, Bug Fix, Infrastructure, Breaking API, File Major, File Minor
- Milestone
See PR Automation & Validation below for details.
</details>
## PR type
<details>
<summary>Help</summary>
- Feature PR:
- Minor/Major change
- Enhancement
- Compilation/dependency change
- Bug fix to an unreleased feature
- Bug Fix PR:
- Bug fix to released code
- Modifications to released documentation
- Infrastructure PR:
- Workflow/process change
- Helper script
- Internal documentation change
- Bug fix to unreleased infrastructure
</details>
**Select exactly one:**
<!-- Selected: '[x]', Unselected: '[ ]' or Click when not in editing mode -->
- [ ] Feature
- [ ] Bug Fix
- [ ] Infrastructure
## Breaking API
<details>
<summary>Help</summary>
Not affecting Infrastructure PRs.
Breaking API includes:
- API breaks
- Not server-firmware API break
- Major file version change
</details>
<!-- Selected: '[x]', Unselected: '[ ]' or Click when not in editing mode -->
- [ ] This is a Breaking API change.
## Description
<!-- Describe what this PR changes and why. -->
## Equivalent PRs
<details>
<summary>Help</summary>
- Equivalent PR is a duplicated PR on another branch (RC or developer).
- If the current PR doesn't have any release notes, link the PR that does.
- Equivalent PRs in RC branches keep release notes instead of developer branch PRs.
</details>
<!-- Link any equivalent PRs using a prefix '#' followed by PR number -->
## Referenced PRs
<details>
<summary>Help</summary>
- Referenced PR is any related PR.
- If the current PR doesn't have any release notes, link the PR that does.
- Eg. Current PR has no release notes when it is a bug fix to an unreleased feature PR that already has release notes.
</details>
<!-- Link any referenced PRs using a prefix '#' followed by PR number -->
## Release notes
<details>
<summary>Help</summary>
Release notes not required for
- Infrastructure PRs
- Chip test board type or developing detector
- PR with release notes linked in equivalent/referenced PR section
</details>
<!-- If release notes required for this PR, describe the user-visible change introduced by this PR below. -->
## Checklist:
<details>
<summary>Before submitting</summary>
- I have chosen the primary PR type.
Feature or Bug Fix PRs:
- I have checked if this is a Breaking API change.
- I have linked any
- equivalent PRs that are on another branch.
- related PRs eg. fixes/additions to an unreleased feature PR.
- I have provided a release note if required
- I have added detector labels. Some automation in adding labels from code change and PR description.
Infrastructure PRs:
- I have linked any equivalent PRs that are in another branch.
</details>
## PR Automation & Validation
<details>
<summary>Additional Information</summary>
List of automation and validations can be found at https://psich.atlassian.net/wiki/x/AQB2P
</details>