build
build copied to clipboard
cli-patch: generalize to-git functionality with PUSH_TO_GITHUB and PUSH_TO_REPO & enable for u-boot as well as kernel
cli-patch: generalize to-git functionality with PUSH_TO_GITHUB and PUSH_TO_REPO & enable for u-boot as well as kernel
- cli-patch: generalize to-git functionality with PUSH_TO_GITHUB and PUSH_TO_REPO & enable for u-boot as well as kernel
-
PUSH_TO_REPO=<url>: set the full git URL to push to -
PUSH_TO_GITHUB=<org>/<repo>: shorthand for pushing to GitHub; setsPUSH_TO_REPO - note: be kind to GitHub, and use forks of torvalds/linux and u-boot/u-boot so GH has a decent base tree
- still, kernel pushes are huge, mostly due to the all-wifi-drivers commit that's always first and always slightly different
- note: when pushing to GitHub, keep in mind the pushed branch contains a GHA workflow, which will only run if you have GHA enabled on the repo
- examples (adapt to your username/forks):
-
./compile.sh BOARD=nanopct6 BRANCH=edge rewrite-kernel-patches PUSH_TO_GITHUB=rpardini/linux -
./compile.sh BOARD=rock-5b BRANCH=legacy rewrite-uboot-patches PUSH_TO_GITHUB=rpardini/armbian-patched-u-boot
-
-
From my perspective, few bits to documentation and its ready to merge.
Completed? Docs bits needed.
Docs could borrow from this PR description. In general, this functionality is not for end-user consumption, but could be very useful for developers, and the original idea was to get the CI jobs that build kernel and u-boot to publish the git tree to repos like armbian/linux and armbian/u-boot (one branch per kernel/board).