Repository navigation
[chore/github]: Standardize GitHub PR description template - #579
Open
oleksandrivantsiv wants to merge 1 commit into
Open
oleksandrivantsiv wants to merge 1 commit into
oleksandrivantsiv wants to merge 1 commit into
Conversation
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
oleksandrivantsiv
force-pushed
the
pr-template-standardization
branch
from
May 21, 2026 22:34
c077717 to
0f16869
Compare
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
This was referenced May 21, 2026
Collaborator
Author
Related PRsThis PR is part of a coordinated rollout to standardize the GitHub PR description template across SONiC repositories. The same change is being applied via the following PRs: |
This was referenced May 21, 2026
Open
Contributor
|
#572 is also open for this purpose. Which one should be used? |
Collaborator
|
@saiarcot895 you please suggest who can review/approve? |
Contributor
@liat-grozovik Please see my comment above. |
Add the standardized pull_request_template.md (description, type, approach, documentation) already used in sonic-swss and sonic-dash-ha, with a patch upstreaming plan/status question for new kernel patches. List the template sections in copilot-instructions.md. Signed-off-by: Oleksandr Ivantsiv <oivantsiv@nvidia.com>
oleksandrivantsiv
force-pushed
the
pr-template-standardization
branch
from
October 7, 2026 22:12
0f16869 to
4224919
Compare
|
/azp run |
|
Azure Pipelines: Successfully started running 1 pipeline(s). |
Collaborator
Author
|
@saiarcot895 This one. I added the patch upstreaming plan/status question you asked for in #572 and closed #572. Please review. |
Collaborator
Author
|
/azpw retry |
|
Retrying failed(or canceled) jobs... |
|
Retrying failed(or canceled) stages in build 1241671: ✅Stage Build:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description of PR
Summary:
Add a GitHub PR description template to this repository: the standardized
template already merged in
sonic-swssandsonic-dash-ha, so contributorssee the same prompts (Description of PR, Type of change, Approach,
Documentation) everywhere across SONiC. For this repository the template also
asks for the patch upstreaming plan/status when new patches are added.
Also update
.github/copilot-instructions.mdso AI-assisted PR descriptionsreference the new template sections.
Type of change
Approach
What is the motivation for this PR?
This repository has no PR description template. A single shared structure
makes reviews predictable: contributors see the same prompts everywhere, and
reviewers can locate the same information in the same place across submodules.
How did you do it?
.github/pull_request_template.md: the standardized template fromsonic-swssandsonic-dash-ha, plus a "Patch upstreaming plan/status (if new patches are being added)" question under Approach..github/copilot-instructions.mdso the "PR description template" guidance lists the sections defined by the new template (Description of PR, Type of change, Approach, Documentation), including the upstreaming question.How did you verify/test it?
No functional changes: only files under
.github/are touched. Verified byrendering the new template on GitHub when opening this PR and confirming all
sections appear correctly.
Any platform specific information?
None.
Documentation
N/A, process/template change only.