Skip to content

Commit

Permalink
Create PULL_REQUEST_TEMPLATE.md
Browse files Browse the repository at this point in the history
Signed-off-by: MD IMRAN <[email protected]>
  • Loading branch information
narmidm committed Nov 9, 2024
1 parent 8868d82 commit 28e6ce7
Showing 1 changed file with 57 additions and 0 deletions.
57 changes: 57 additions & 0 deletions .github/PULL_REQUEST_TEMPLATE.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,57 @@
<!--
For Work In Progress Pull Requests, please use the Draft PR feature,
see https://github.blog/2019-02-14-introducing-draft-pull-requests/ for further details.
For a timely review/response, please avoid force-pushing additional
commits if your PR already received reviews or comments.
Before submitting a Pull Request, please ensure you've done the following:
- 📖 Read the Contributing Guide: https://github.com/kubeslice/docs/blob/master/CONTRIBUTING.md
- 📖 Read the Code of Conduct: https://github.com/kubeslice/docs/blob/master/code_of_conduct.md
- 👷‍♀️ Create small PRs. In most cases this will be possible.
- ✅ Provide tests for your changes.
- 📝 Use descriptive commit messages.
- 📗 Update any related documentation and include any relevant screenshots.
NOTE: Pull Requests from forked repositories will need to be reviewed by
a KubeSlice Team member before any CI builds will run.
-->

## What type of PR is this? (check all applicable)

- [ ] Refactor
- [ ] Upgrades
- [ ] Documentation Update

## Description

## Related Tickets & Documents

<!--
For pull requests that relate or close an issue, please include them
below. We like to follow [Github's guidance on linking issues to pull requests](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue).
For example having the text: "closes #1234" would connect the current pull
request to issue 1234. And when we merge the pull request, Github will
automatically close the issue.
-->

- Related Issue #
- Closes #

## QA Instructions, Screenshots, Recordings

_Please replace this line with instructions on how to test your changes, a note
on the devices and browsers this has been tested on, as well as any relevant
images for UI changes._

### UI accessibility checklist
_If your PR includes UI changes, please utilize this checklist:_
- [ ] Semantic HTML implemented?
- [ ] Keyboard operability supported?
- [ ] Color contrast tested?


## [optional] What gif best describes this PR or how it makes you feel?

![WoW](https://media.giphy.com/media/v1.Y2lkPTc5MGI3NjExMmV3dmxidWpiN2Jlb21rOGNjcXZhemN4bGR0cHBpNW1rd2w4dW9haSZlcD12MV9pbnRlcm5hbF9naWZfYnlfaWQmY3Q9Zw/tIeCLkB8geYtW/giphy.gif)

0 comments on commit 28e6ce7

Please sign in to comment.