From d5c9e68a3ee9fa2b30d6f8811afae94ee79e5d6a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Elena=20Torr=C3=B3?= Date: Fri, 7 Mar 2025 14:45:29 +0100 Subject: [PATCH] :wrench: Update pull request GitHub template (#6022) --- .github/PULL_REQUEST_TEMPLATE.md | 36 ++++++++++++-------------------- 1 file changed, 13 insertions(+), 23 deletions(-) diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md index e4a4e3c7bb..70b6bb00df 100644 --- a/.github/PULL_REQUEST_TEMPLATE.md +++ b/.github/PULL_REQUEST_TEMPLATE.md @@ -1,29 +1,19 @@ - - 1. Select which branch should this PR be merged in? By default, you should always merge to the develop branch. - 2. PR name follows [convention](http://karma-runner.github.io/4.0/dev/git-commit-msg.html) - 3. All tests pass locally, UI and Unit tests - 4. All business logic and validations must be on the server-side - 5. Update necessary Documentation - 6. Put `closes #XXXX` in your comment to auto-close the issue that your PR fixes +### Summary +### Steps to reproduce -Also, if you're new here +### Checklist -- Contribution Guide => https://github.com/uxbox/uxbox/blob/develop/CONTRIBUTING.md +- [ ] Choose the correct target branch; use `develop` by default. +- [ ] Provide a brief summary of the changes introduced. +- [ ] Add a detailed explanation of how to reproduce the issue and/or verify the fix, if applicable. +- [ ] Include screenshots or videos, if applicable. +- [ ] Add or modify existing integration tests in case of bugs or new features, if applicable. +- [ ] Check CI passes successfully. +- [ ] Update the `CHANGES.md` file, referencing the related GitHub issue, if applicable. ---> - -> Please provide enough information so that others can review your pull request: - - - -> Explain the **details** for making this change. What existing problem does the pull request solve? - - - -> Screenshots/GIFs - - +