[Feature request] A new `git` version string that builds from the literal latest commit

[Ciel-MC]

This might be a little weird, but I saw that inlay_hint got changed into inlay_hint.enable, so I wanted to update my config to fit it, but I found that the latest nightly does not have that commit included yet, and I don't see there being any way to get the latest git(latest seems to be the same as stable), so I had to grab the latest commit at the time myself and install that, so I thought it'd be nice to have a version tag git which will simply grab the newest commit and build with that.

[MordechaiHadad]

Don't think I am following what you are trying to do, bob deals with 2 types of neovim files, binaries (nightly, stable and older versions) and source code so you can choose a specific commit paste it with bob install <commit hash> and it will build it for you.

[Ciel-MC]

Yeah, and I was hoping there can be a "version name"(like stable or nightly) for the latest commit, like even faster than nightly, because now if I manually set the latest commit to my version, it doesn't update with bob update because it is pinned.

[MordechaiHadad]

So you want an alias for the last commit when running bob install?

[Ciel-MC]

So you want an alias for the last commit when running bob install?

I guess you can say an alias? But also when you do bob update, it installs the latest commit(like latest and nightly)

[MordechaiHadad]

What would you call this alias?

[Ciel-MC]

I figured git would be a good name, similar to how AUR repos call it

[max397574]

Imo there is no need for this feature. Just wait for maximum 24 hours and then do bob install nightly. If you really want a feature just use the commit hash to install that specific commit. KISS

[Ciel-MC]

I had this debate with myself as well, but the thing for me is that it's often not just this one time I want to do it(so I install the latest manually, uninstall tomorrow and update nightly), I would prefer if I could stay on the latest commit easily as you can with stable and nightly, at least personally, found it to be barely make past the -100 pts, plus it's not a particularly difficult feature either, and maybe it will come in helpful in the future.

Sorry, long sentences from me are very coherent, my point is, I think this is not complicated enough and is quite helpful when you need/want it, even if it's not often.

P.S. KISS is usually for designing systems, features typically use the -100pt rule

[max397574]

even if "the official" KISS rule doesn't apply here I'm always against adding features that bring no big advantage to the user but cause more complicated code (here new logic needs to be added to get the latest commit) and also would make the whole application more complicated (e.g. bigger help etc).

and if you waited for weeks for a pr to be merged you can easily wait a few more hours imo.

[MordechaiHadad]

🤔

[MordechaiHadad]

I will work on this, but it won't be a priority because it is slightly more complicated than expected

[NonlinearFruit]

Something like this works if you have a get-github-token command or equivalent.

AUTH="Authorization: token $(get-github-token)"
SHA="$(curl -s -H "$AUTH" -H "Accept: application/vnd.github.VERSION.sha" https://api.github.com/repos/neovim/neovim/commits/master)"
bob install "$SHA"

Using a script like this could be a middle ground if nightly's are to slow and bob doesn't have a latest commit alias

[MordechaiHadad]

@Ciel-MC Pretty late (I worked on this when you opened the issue but the solution originally was too complex) but the request is fulfilled.