Skip to content
This repository has been archived by the owner on Dec 8, 2024. It is now read-only.

Latest commit

 

History

History
50 lines (35 loc) · 3.17 KB

File metadata and controls

50 lines (35 loc) · 3.17 KB
08/MAY/2024:

RVX development was resumed.

07/AUGUST/2023:

Merged new upstream features...

15/JULY/2023:

Merged upstream changes...

  • Now with support for RVX Reddit.

Also supports the other Reddit clients, such as RV Sync.

  • Read the README-ORIGINAL.md for more information about those in the original repository.
23/MARCH/2023:

Builds are now automated!

Added simple scheduled action that checks for patch updates, and if an update is found, records the new version of patches for future reference and automatically triggers the workflow to build and release the new applications.


Feel free to fork this fork.

Let the 'forkception' begin!

How to use this fork:

Before running the workflows for the first time, you need to go the Settings page of the repository and under Actions, then General, change the "Workflow permissions" to "read and write".

  1. Go to the Actions page at the top.
  2. Select the "Build & Release" action.
  3. Click the "Run Workflow" drop-down button and run it.

    Optionally, select the "Update Checker" action, and enable it. It will periodically check for new inotia00/revanced-patches releases and trigger a new Build & Release when a new version is found.

    You may change the repository to watch for updates in the update.yml [line 28] workflow file.

It will take around 7 minutes to complete the Build & Release workflow. Once that's completed:

  1. Go to "Releases" at the bottom of your repository page (on mobile) or at the right (on Desktop).
  2. Download your patched applications.

Set up to build:

Check .env for a list of excluded patches and options.json for patch options.
Complete and original README can be found here.