-
Notifications
You must be signed in to change notification settings - Fork 700
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
try to figure out why static builds lack git info #10693
base: master
Are you sure you want to change the base?
Conversation
a186c91
to
a9c0a0c
Compare
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.
In the interest of experimenting, this could be fast-tracked, I hope.
a9c0a0c
to
7c3bcff
Compare
7c3bcff
to
4c8ca38
Compare
If it's "ready for review", maybe un-draft it too? |
Haven't yet modified the git stuff to degrade gracefully on lack of git info yet; been focused on trying to make the Alpine job provide it. |
All right, it's up to you, of course. In my mind, these were separate issues. But I guess it may be more ergonomic to kill two birds with one PR! |
try to figure out why static builds lack git info
Please read Github PR Conventions and then fill in one of these two templates.
Template B: This PR does not modify behaviour or interface
E.g. the PR only touches documentation or tests, does refactorings, etc.
Include the following checklist in your PR: