Skip to content

Add PR template and align copilot-instructions #572

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.

Sign up for GitHub

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

Open
oleksandrivantsiv wants to merge 1 commit into
base: master
Choose a base branch
from
+25 −0
Open

Add PR template and align copilot-instructions #572

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
6 changes: 6 additions & 0 deletions .github/copilot-instructions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -76,6 +76,12 @@ Kernel patches are accepted under these conditions:
- **Upstream first**: Prefer upstream patches — include the original commit hash
- **Justification**: Explain why a patch is needed and why it can't be done out-of-tree
- **CI**: Azure pipeline checks must pass
- **PR description template**: Fill out all sections of the [PR template](pull_request_template.md) when submitting a pull request:
- **What I did**: Summarize the change being made
- **Why I did it**: Explain motivation and context for the change
- **How I verified it**: Provide steps or commands to test the change
- **Details if related**: Include any additional context, links, or related information


## Gotchas

Expand Down
19 changes: 19 additions & 0 deletions .github/pull_request_template.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
<!--
Please make sure you have read and understood the contribution guildlines:
https://github.com/Azure/SONiC/blob/gh-pages/CONTRIBUTING.md

1. Make sure your commit includes a signature generted with `git commit -s`
2. Make sure your commit title follows the correct format: [component]: description
3. Make sure your commit message contains enough details about the change and related tests
4. Make sure your pull request adds related reviewers, asignees, labels

Please also provide the following information in this pull request:
-->

**What I did**

**Why I did it**

**How I verified it**

**Details if related**