What the feature should be
We currently use a SHA256 hash to identify a commit. Which is great, but they are very long and cumbersome to actually use.
Instead of requiring the whole hash to be provided, all we really need is a long enough prefix to uniquely identify one commit - This is what git does, for good reason.
How this feature should be triggered
Implicitly, whenever a commit reference is passed on the commandline, we should check whether it uniquely identifies a commit, instead of whether it exactly matches one.
Why this feature should be added
It would make it much easier to use hero when not on a branch tip.
What the feature should be
We currently use a SHA256 hash to identify a commit. Which is great, but they are very long and cumbersome to actually use.
Instead of requiring the whole hash to be provided, all we really need is a long enough prefix to uniquely identify one commit - This is what git does, for good reason.
How this feature should be triggered
Implicitly, whenever a commit reference is passed on the commandline, we should check whether it uniquely identifies a commit, instead of whether it exactly matches one.
Why this feature should be added
It would make it much easier to use
herowhen not on a branch tip.