需先修改 patches/build.gradle.kts 中的项目 group 与 About 信息;发布前需配置 GPG_PRIVATE_KEY、GPG_PASSPHRASE、GPG_FINGERPRINT 三个仓库 secret;构建流程需参照 ReVanced 官方文档,README 未给出具体命令
revanced-patches-template
ReVancedGPL-3.0更新放缓ReVanced 补丁模板仓库,提供 Kotlin 项目骨架,方便开发者快速创建自定义 Android 应用补丁,用于修改和扩展应用功能。
👋🧩Template repository for ReVanced Patches
git clone https://github.com/ReVanced/revanced-patches-templateREADME 未说明
ReVanced 补丁仓库模板,帮你快速搭一个自己的补丁项目
ReVanced 补丁模板仓库,提供 Kotlin 项目骨架,方便开发者快速创建自定义 Android 应用补丁,用于修改和扩展应用功能。
核心能力
- 基于模板一键创建新的 ReVanced Patches 仓库
- 支持在同一仓库内维护多个补丁并与其他仓库补丁共用
- 内置 release.yml 工作流自动发布并生成 changelog
- 提供 buildAndroid 任务构建可在 Android 上使用的补丁
- 采用语义化版本与语义化提交规范管理补丁
容易踩的坑
- v1.0.5-dev.1pre-release2026-02-21 · 2026-02-21 23:15 UTC
查看更新说明
1.0.5-dev.1 (2026-02-21)
- v1.0.4最新正式版2024-11-05 · 2024-11-05 19:17 UTC
1.0.4 (2024-11-05)
- v1.0.4-dev.2pre-release2024-11-05 · 2024-11-05 19:01 UTC
查看更新说明
1.0.4-dev.2 (2024-11-05)
- v1.0.4-dev.1pre-release2024-09-30 · 2024-09-30 20:51 UTC
查看更新说明
1.0.4-dev.1 (2024-09-30)
- v1.0.32024-09-08 · 2024-09-08 17:17 UTC
用户点评
登录用户的真实使用记录,可按版本和硬件筛选还没有人点评。第一个说出真实体验的人最有价值。
👋🧩 ReVanced Patches template
Template repository for ReVanced Patches.
❓ About
This is a template to create a new ReVanced Patches repository.
The repository can have multiple patches, and patches from other repositories can be used together.
For an example repository, see ReVanced Patches.
🚀 Get started
To start using this template, follow these steps:
- Create a new repository using this template
- Set up the build.gradle.kts file (Specifically, the group of the project, and the About)
- Update dependencies in the libs.versions.toml file
- Create a pass-phrased GPG master key and subkey
- Add the private key as a secret named GPG_PRIVATE_KEY to your repository
- Add the passphrase as a secret named GPG_PASSPHRASE to your repository
- Add the fingerprint of the GPG subkey as a secret named GPG_FINGERPRINT to your repository
- Set up the README.md file1 (e.g, title, description, license, summary of the patches that are included in the repository), the issue templates2 and the contribution guidelines3
🎉 You are now ready to start creating patches!
🔘 Optional steps
You can also add the following things to the repository:
- API documentation, if you want to publish your patches as a library
🧑💻 Usage
To develop and release ReVanced Patches using this template, some things need to be considered:
- Development starts in feature branches. Once a feature branch is ready, it is squashed and merged into the
devbranch - The
devbranch is merged into themainbranch once it is ready for release - Semantic versioning is used to version ReVanced Patches. ReVanced Patches have a public API for other patches to use
- Semantic commit messages are used for commits
- Commits on the
devbranch andmainbranch are automatically released via the release.yml workflow, which is also responsible for generating the changelog and updating the version of ReVanced Patches. It is triggered by pushing to thedevormainbranch. The workflow uses thepublishtask to publish the release of ReVanced Patches - The
buildAndroidtask is used to build ReVanced Patches so that it can be used on Android. Thepublishtask depends on thebuildAndroidtask, so it will be run automatically when publishing a release.
📚 Everything else
📙 Contributing
Thank you for considering contributing to ReVanced Patches template.
You can find the contribution guidelines here.
🛠️ Building
To build ReVanced Patches template, you can follow the ReVanced documentation.
📜 Licence
ReVanced Patches template is licensed under the GPLv3 licence. Please see the license file for more information. tl;dr you may copy, distribute and modify ReVanced Patches template as long as you track changes/dates in source files. Any modifications to ReVanced Patches template must also be made available under the GPL, along with build & install instructions.