Skip to content

Commit

Permalink
chore: update pr template (#2956)
Browse files Browse the repository at this point in the history
* chore: update pr template

* chore: address comments

* Update .github/pull_request_template.md

Co-authored-by: Krishna Chaitanya <[email protected]>

* Update .github/pull_request_template.md

Co-authored-by: Krishna Chaitanya <[email protected]>

* chore: updated checklist

* chore: fix linear, heading

---------

Co-authored-by: Krishna Chaitanya <[email protected]>
  • Loading branch information
yashasvibajpai and krishna2020 authored Dec 27, 2023
1 parent 5cd953d commit 4e1a200
Showing 1 changed file with 15 additions and 19 deletions.
34 changes: 15 additions & 19 deletions .github/pull_request_template.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,21 +2,15 @@

Write a brief explainer on your code changes.

## Please explain the objectives of your changes below

Put down any required details on the broader aspect of your changes. If there are any dependent changes, **mandatorily** mention them here

### Type of change
## What is the related Linear task?

If the pull request is a **bug-fix**, **enhancement** or a **refactor**, please fill in the details on the changes made.
Resolves INT-XXX

- Existing capabilities/behavior

- New capabilities/behavior
## Please explain the objectives of your changes below

If the pull request is a **new feature**,
Put down any required details on the broader aspect of your changes. If there are any dependent changes, **mandatorily** mention them here

### Any technical or performance related pointers to consider with the change?
### Any changes to existing capabilities/behaviour, mention the reason & what are the changes ?

N/A

Expand All @@ -28,25 +22,27 @@ N/A

N/A

### If the PR has changes in more than 10 files, please mention why the changes were not split into multiple PRs.

N/A

### If multiple linear tasks are associated with the PR changes, please elaborate on the reason:
### Any technical or performance related pointers to consider with the change?

N/A

<hr>

### Developer checklist

- [ ] My code follows the style guidelines of this project

- [ ] **No breaking changes are being introduced.**

- [ ] Are all related docs linked with the PR?
- [ ] All related docs linked with the PR?

- [ ] All changes manually tested?

- [ ] Any documentation changes needed with this change?

- [ ] Are all changes manually tested?
- [ ] Is the PR limited to 10 file changes?

- [ ] Does this change require any documentation changes?
- [ ] Is the PR limited to one linear task?

- [ ] Are relevant unit and component test-cases added?

Expand Down

0 comments on commit 4e1a200

Please sign in to comment.