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.

Sign up for GitHub

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

Jump to bottom

use full-gitsha #67

Open

line-o opened this issue Feb 10, 2025 · 0 comments

Assignees

Member

line-o commented Feb 10, 2025

Instead of using shortened hashes to identify commits tuttle will always use the entire hash.

This is a breaking change in so far that a full installation is needed in order to write the hash in the expected format.

Alternative approach: Find out if the shortened sha can be used as a fallback when dealing with older installations

line-o self-assigned this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment