|
| 1 | +# Pull Request Template for the Bash_setup Project |
| 2 | + |
| 3 | +## Description |
| 4 | + |
| 5 | +Please provide a summary of the changes made, including: |
| 6 | +- The issue(s) fixed or the enhancement(s) added. |
| 7 | +- Relevant motivation and context for the change. |
| 8 | +- Any dependencies required for this update. |
| 9 | + |
| 10 | +--- |
| 11 | + |
| 12 | +## Type of Change |
| 13 | + |
| 14 | +Please select the type of change by marking the relevant option(s) with `[x]`: |
| 15 | +- [ ] Bug fix (non-breaking change that fixes an issue) |
| 16 | +- [ ] New feature (non-breaking change that adds functionality) |
| 17 | +- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) |
| 18 | +- [ ] Documentation update (adds or modifies documentation) |
| 19 | +- [ ] Third-party dependency update (e.g., new tools, libraries, or resources) |
| 20 | + |
| 21 | +--- |
| 22 | + |
| 23 | +## How Has This Been Tested? |
| 24 | + |
| 25 | +Describe the tests you ran to verify your changes, including: |
| 26 | +1. Commands executed to validate the script's behavior. |
| 27 | +2. Environment details: |
| 28 | + - Operating System and version (e.g., Ubuntu 20.04, macOS Ventura). |
| 29 | + - Bash version (`bash --version`). |
| 30 | + - Any relevant configurations or dependencies used for testing. |
| 31 | +3. Test results: |
| 32 | + - Example input and output for the changes. |
| 33 | + |
| 34 | +**Testing Checklist:** |
| 35 | +- [ ] Local testing with various edge cases and normal inputs. |
| 36 | +- [ ] Verified compatibility with related scripts/modules. |
| 37 | +- [ ] Reviewed logging outputs (if applicable). |
| 38 | + |
| 39 | +--- |
| 40 | + |
| 41 | +## Screenshots (If Applicable) |
| 42 | + |
| 43 | +If the changes involve user-facing functionality or outputs, please include **before and after screenshots** to help reviewers understand the impact of the change. |
| 44 | + |
| 45 | +--- |
| 46 | + |
| 47 | +## Checklist |
| 48 | + |
| 49 | +Please complete the checklist below to ensure your PR meets the project standards: |
| 50 | + |
| 51 | +- [ ] I have run `shellcheck` using the repository's `.shellcheckrc` file to verify linting: |
| 52 | + ```bash |
| 53 | + shellcheck --shell=bash --external-sources -x -S style -f gcc <your-script.sh> |
| 54 | + ``` |
| 55 | +- [ ] I have formatted all scripts using `shfmt`: |
| 56 | + ```bash |
| 57 | + shfmt -i 4 -ci -bn -kp -sr -ln bash -d . |
| 58 | + ``` |
| 59 | +- [ ] I have verified that my changes are consistent with the project's [Style Guide](./STYLEGUIDE.md). |
| 60 | +- [ ] I have updated or added relevant tests (e.g., unit tests, test scripts). |
| 61 | +- [ ] All existing tests pass successfully after my changes. |
| 62 | +- [ ] I have added or updated documentation as needed, and linked any relevant PRs in related repositories (e.g., documentation or tools). |
| 63 | +- [ ] I have reviewed my own code for clarity and correctness. |
| 64 | +- [ ] I have commented on particularly complex or non-obvious parts of the code. |
| 65 | + |
| 66 | +--- |
| 67 | + |
| 68 | +## Additional Notes |
| 69 | + |
| 70 | +If your changes rely on external tools or third-party dependencies, please include details about: |
| 71 | +1. Why the tool/dependency is required. |
| 72 | +2. Links to relevant documentation or PRs in those third-party projects. |
| 73 | + |
| 74 | +--- |
| 75 | + |
| 76 | +This PR template is designed to ensure contributions to the **bash_setup** project are clear, well-tested, and maintainable. Thank you for your contribution! |
| 77 | + |
0 commit comments