To fix this, create a new organization, fork to the new organization. This fixes the problem, for now.
If your recovery tree has prebuilt kernel, move to this
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
-
Set the variables, as listed below.
Update : If you don't understand the manifest command, check this
Some variables that you'd like to set:
MANIFEST : Link to your recovery manifest, Google it if you don't know what this is
DEVICE : Most likely your device codename, e.g. rosy, sakura, curtana, etc.
DT_LINK : Link to your recovery device tree.
DT_PATH : Path to clone your device tree
KERNEL_LINK : Link to your device kernel source
KERNEL_PATH : Path to clone your kernel tree
TARGET : recoveryimage or bootimage, depending on if your phone has a recovery partition or not
-
Go to actions tab, enable workflows.
-
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.