-
Notifications
You must be signed in to change notification settings - Fork 175
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add warning that ublue-os/startingpoint image won't be updated anymore #80
Comments
ublue-os/startingpoint is not meant to be rebased on and that's never been recommended by any part of documentation. If you've made your own fork, when merging / rebasing on new changes, you should see the additions in the documentation telling you to create a branch called If there's any confusion you feel is not adequately covered by these, please comment below on where you think a notice should be added. |
Then maybe the old package should be deleted? |
Sure! I can't do that tho (@castrojo) It also seems that my personal image got built too when I accidentally pushed my own repo's live branch into this repo (smh) https://github.com/ublue-os/startingpoint/pkgs/container/linuxyz, so that should be deleted too. |
Done! |
Looks good to me. |
I think this will confuse newcomers because the startingpoint image does not get pushed after PR #76.
The text was updated successfully, but these errors were encountered: