Skip to content

Commit

Permalink
Create PULL_REQUEST_TEMPLATE.md
Browse files Browse the repository at this point in the history
  • Loading branch information
eliasjpr authored Dec 13, 2024
1 parent 8a1a0c0 commit bc079e5
Showing 1 changed file with 67 additions and 0 deletions.
67 changes: 67 additions & 0 deletions .github/PULL_REQUEST_TEMPLATE.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,67 @@
Here is a suggested **Pull Request Template** for your repository:

---

## **Pull Request Template**

### **Description**

<!-- Please provide a brief summary of the changes you are making. -->
- What issue does this solve? (If applicable, link to the issue)
- Key points or highlights of the changes.

---

### **Type of Change**

<!-- Check all that apply -->
- [ ] 🐛 Bug fix
- [ ] ✨ New feature
- [ ] 🔒 Security update
- [ ] 🧹 Code refactor/cleanup
- [ ] 📚 Documentation update
- [ ] 🔧 Build/CI update

---

### **Checklist**

<!-- Ensure your Pull Request adheres to the project standards -->
- [ ] Code builds and runs locally without errors.
- [ ] All tests pass (run `bundle exec rspec` or equivalent for the project).
- [ ] Added or updated documentation (e.g., README, inline comments).
- [ ] Added or updated tests to cover changes.
- [ ] Linked to related issue(s) or pull request(s).

---

### **Steps to Test Changes**

<!-- Provide steps to test the changes locally -->
1. Clone this branch: `git clone -b <branch-name> https://github.com/azutoolkit/joobq.git`
2. Run: `<provide commands for building/running/testing>`
3. Verify: `<expected outcome>`

---

### **Related Issues**

<!-- List any related issues or pull requests -->
- Resolves: #
- Related: #

---

### **Screenshots (if applicable)**

<!-- Add any relevant screenshots or screencasts to demonstrate changes -->

---

### **Additional Notes**

<!-- Any other context about the changes that might be helpful for the reviewers. -->

---

*Thank you for contributing to JoobQ! We value your time and effort!*

0 comments on commit bc079e5

Please sign in to comment.