Upcoming rewrite of git history #103
facchinm
announced in
Announcements
Replies: 1 comment
-
Maybe something like git stash will still allow you to get around this. I usually have run into this with the current stuff anyway as I But I can also imagine we might need to do a fresh reload after this PR is done! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi everyone
Since we are approaching a beta2 stage, we'd like to cleanup the repo before it's too late 🙂
To keep things "easy", we used to commit
llext-edk
andfirmwares
folders, and this creates a couple of problems, namely:So we overhauled the CI and use it as an artifact provider! When #102 will be merged, every time we push to
main
, the compiled files will be uploaded to our servers, ready to be retrieved by a fancy utility in the exact expected status.This will primarily benefit users who don't want to install the whole zephyr toolchain to just modify the core/library files, while the "hardcore" users will not see any change in their workflow (except a much cleaner git history 😉 )
The only drawback (@KurtE @mjs513) is that
git pull
will not sync anymore after the merge (if coming from an "uncleaned" core) so the core will need to be redownloaded 😞Beta Was this translation helpful? Give feedback.
All reactions