external/revanced-patcher
1
0
Fork 0
mirror of https://github.com/ReVanced/revanced-patcher.git synced 2024-11-10 01:02:22 +01:00
Code Issues Projects Releases Packages Wiki Activity
revanced-patcher/CONTRIBUTING.md
oSumAtrIX 26d449e6d9 docs: Fix broken links
2024-08-06 16:53:42 +02:00

5 KiB
Raw Blame History


                       

Continuing the legacy of Vanced

👋 Contribution guidelines

This document describes how to contribute to ReVanced Patcher.

📖 Resources to help you get started

  • The documentation contains the fundamentals of ReVanced Patcher and how to use ReVanced Patcher to create patches
  • Our backlog is where we keep track of what we're working on
  • Issues are where we keep track of bugs and feature requests

🙏 Submitting a feature request

Features can be requested by opening an issue using the Feature request issue template.

Note

Requests can be accepted or rejected at the discretion of maintainers of ReVanced Patcher. Good motivation has to be provided for a request to be accepted.

🐞 Submitting a bug report

If you encounter a bug while using ReVanced Patcher, open an issue using the Bug report issue template.

📝 How to contribute

  1. Before contributing, it is recommended to open an issue to discuss your change with the maintainers of ReVanced Patcher. This will help you determine whether your change is acceptable and whether it is worth your time to implement it
  2. Development happens on the dev branch. Fork the repository and create your branch from dev
  3. Commit your changes
  4. Submit a pull request to the dev branch of the repository and reference issues that your pull request closes in the description of your pull request
  5. Our team will review your pull request and provide feedback. Once your pull request is approved, it will be merged into the dev branch and will be included in the next release of ReVanced Patcher

❤️ Thank you for considering contributing to ReVanced Patcher,
ReVanced