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
heroku 6.12.3 #15318
heroku 6.12.3 #15318
Conversation
@dickeyxxx thanks! By the way, you may want to start using 8 digit hashes for these, instead of 7, since that is the length Git chooses for your repo size now. https://github.com/heroku/cli/commit/fca882c43e2570f79614bbb5fcb863bb2a5f69a9.patch Note |
that might be github doing that, we run BTW we're still discussing the build stuff, hope to reach out soon with that but I've got a few things going on at the moment. |
Excellent!
It's actually just caused by Git >= 2.11.0 which uses a dynamic length instead of 7 for the short hashes. See https://github.com/blog/2288-git-2-11-has-been-released (We had some issues related to this recently #13792) Luckily there's a new GitHub feature ( https://github.com/heroku/cli/commit/fca882c43e2570f79614bbb5fcb863bb2a5f69a9.patch?full_index=1
|
(So Homebrew Core https://github.com/Homebrew/homebrew-core.git has a variable short hash length of 10). So I think https://github.com/heroku/cli-engine/blob/master/bin/version#L2 is correct but you must be using an older Git in your backend that still hard codes length 7 instead of the dynamic length. |
hrm. I'm on git 2.13.2 and it's sending 7 digit hashes. The point may be moot though (see my next PR) |
Yeah, locally I get 7 for your repo
The backend GitHub repo for your repository must be a bit larger than the user-facing one. Interesting. |
Thanks for the upgrade! Merged! |
Created with
brew bump-formula-pr
.