To fix this, create a new organization, fork to the new organization. This fixes the problem, for now.
This is an easy way for recovery maintainers or anyone who's interested in building recoveries to finish their dream without a server.
This works with GitHub actions, thank GitHub not me.
Here are some useful notes to using this tool brewed with black magic.
-
Fork the repo to a organization
-
Go to action
-
Select "Building recovery" Workflow
-
Enter the variables which are mentioned
MANIFEST : Link For Minimal Recovery Manifest; default is twrp minimal manifest
MANIFEST_BRANCH : Enter Manifest Branch Would You Like To Sync like, e.g. twrp-11
DT_LINK : Enter Link For Your Device Tree With Branch Like $URL -b BRANCH
VENDOR : Enter Your Device OEM, e.g. motorola, asus, xiaomi, etc.
DEVICE : Enter Your Device Code Name, e.g. rosy, sakura, curtana, etc.
LUNCHCMD : Enter Lunch Command like lunch omni_$device-eng or lunch twrp_$device-eng
BUILDCMD : Enter Build Command m recoveryimage or m bootimage
TW_DEVICE_VERSION : Set Custom Build Version
GH_TOKEN : Add GitHub Token in Secret Environment
Optional
EXTRA_CMD : Add Extra Commands To Run Before Build Start
-
Click On "Run Workflow"
-
Star the repo, go to actions tab again, and let black magic go brrr.
If you don't know any of these, Ask Google or someone who builds recoveries, I don't provide TWRP building support.
You'd also like to do edits on your recovery device tree first if your recovery needs that (e.g. SHRP, etc.)
Made with blek magic by Jamie
Infinite help from ElytrA8
Recovery building help from Pulkit
And lastly, all TWRP compiling help from Google.
Enjoy buildbotting.