-
Notifications
You must be signed in to change notification settings - Fork 177
Don't retrieve repository's SHA in prebuild step. #1426
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
Conversation
Doing this means source can only be built when checked out from git, and can't be build from an archive.
The following links are available: build (ubuntu-18.04, full)
build (macOS-10.15, full) build (self-hosted_debian-11_aarch64, full)
build (windows-latest, full) |
Is it not possible that this check is meant for automated builds / checking consistency to ensure what's being built is the same as another? What about just converting it to throw a log message or two upon failure but not actually stop the build from continuing? |
@digisomni Maybe, but I don't think we really need it to be here. If you're checking out something from git in GHA, Jenkins or such, it's trivial to get the commit's hash right there. I think that's where such code should go. This change was made to make it easier to generate packages. Currently builds fail if you try to build against a .zip downloaded from github due to this code. |
It is also good to simplify the build system and reduce dependencies. |
Good point, if we want SHA checking it may be included in whatever CI/CD application it is. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It built on all platforms so I assume that all instances were caught.
Doing this means source can only be built when checked out from git and can't be build from an archive.
It's also completely useless. All that's being done is outputting it into the log.