ceos/universal-android-debloater-next-generation
1
0
Fork 0
mirror of https://github.com/Universal-Debloater-Alliance/universal-android-debloater-next-generation.git synced 2026-08-09 15:19:11 +02:00
Code Issues Projects Releases Packages Wiki Activity
universal-android-debloater.../.github/PULL_REQUEST_TEMPLATE/documentation.md
Anonymoussaurus a5136a6674
 chore(pull-request-templates): add templates (#1283) 
* chore(pull-request-template): add templates

Introduce two pull request templates to standardize contributions: .github/pull_request_template/app.md for app-related changes (description, related issues, testing matrix, checklist) and .github/pull_request_template/packages.md for package updates (description, testing, acknowledgements, package validation checklist). These templates help ensure consistent PR metadata and verification steps for maintainers and contributors.

* chore(pull-request-templates): add documentation template

Add .github/pull_request_template/documentation.md to provide a standardized pull request template for documentation updates. The template includes a Description section, Documentation Changes section, and a checklist (link to CONTRIBUTING, clarity, grammar/spelling, link verification, code example testing, and markdown formatting) to improve consistency and quality of doc PRs.

* chore(pull-request-templates): add desktop/window manager fields

Add 'Desktop Environment' and 'Window System/Manager' checklist items to the app PR template to capture more detailed testing environment information. Also adjust the ADB version line indentation to align with the checklist structure.

* chore(pull-request-templates): use absolute URL for contributing guidelines

* chore(pull-request-templates): move files to dedicated folder

* chore(pull-request-template): reword checkbox

Co-authored-by: Angel J <78835633+iamanaws@users.noreply.github.com>

---------

Co-authored-by: Angel J <78835633+iamanaws@users.noreply.github.com>
2026-02-18 10:52:31 -04:00

862 B
Raw Blame History

Description

Documentation Changes

Checklist

  • I have read the CONTRIBUTING guidelines
  • My changes are clear and easy to understand
  • I have checked for grammar and spelling errors
  • I have verified all links are correct
  • I have tested any code examples provided
  • The documentation is properly formatted with markdown