-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Fetch particular git hash remotely in pi-gen releases #442
base: master
Are you sure you want to change the base?
Conversation
Probably makes more sense to remove that line or set it to some text saying it's not from a git repo. People who forked the repo wouldn't want that URL hard-coded in there and there's nothing to say that what's on github matches their local files in any way. |
Probably, it won't be a good idea to remove the line as in
This avoids hardcoding the URL. If this deems suitable, will modify the commit accordingly. |
build-docker is just passing it on so that it's not lost in the container. If it ends up being unset, it should end up being handled the same way. It would be good to avoid something that looks like a valid git hash if it's not. Something like 'local' could be used instead? |
|
I don't quite agree with the logic that the git hash will match what it gets from the remote tags, but if it's good enough for your use case, I have no problem with it. Happy for it to be merged, or would you like to make any changes? |
git hash ends up in
Without, the patch,
The abovementioned patched image is generated wth |
This should be ok now. |
Couple of shellcheck issues:
Unless I missed something, |
Hopefully, it would be fine this time. |
Any updates on this? |
GIT_HASH is not calculated properly in pi-gen releases as there is no git setup in releases archives. This commit fetches the release's corresponding commit hash remotely from pi-gen repo.