Skip to content
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

fix: replace vergen by directly running git #28

Merged
merged 1 commit into from
Dec 12, 2023
Merged

Conversation

aochagavia
Copy link
Collaborator

For some reason, vergen was unable to find the git binary when building inside Ansible. Running git directly fixes the problem... and we also have one dependency less! 🎉

Fixes #27

For some reason, `vergen` was unable to find the git binary when
building inside Ansible. Running git directly fixes the problem... and
we also have one dependency less! 🎉
@aochagavia
Copy link
Collaborator Author

I'm puzzled to see that the solution was so simple... I guess I should be more skeptical of dependencies in the future, instead of blaming ansible 😅.

Merging right away since we already discussed this.

@aochagavia aochagavia merged commit 3c513e6 into main Dec 12, 2023
9 checks passed
@aochagavia aochagavia deleted the info-take-2 branch December 12, 2023 08:50
Copy link
Member

@cpu cpu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice! Glad this worked out.

I thought to wonder about the need for vergen in my initial review but hesitated. Next time I'll pull on the "do we need a dependency?" thread a bit harder too :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Build fails to access git executable
2 participants