Add @nightly to gh

[eirikb]

@koppor what do you think about adding @nightly to gh?

You might have heard of https://nightly.link/ . The point is to link to latest successful build, instead of releases.
For example: https://github.com/cli/cli/actions/runs/15333323202

The reason is that not all projects have releases, and in that case gg won't work.

Security wise gg would IMHO be much safer, as you see nightly.link now points to itself instead of direct artifact link. Meaning user will go to nightly.link to download the actual binary (scary scary) - although in reality nightly.link will redirect to GitHub, which also redirects - but entry point is not GH!
For example:
https://github.com/ayn2op/discordo/
Which only relies on this, by linking to https://nightly.link/ayn2op/discordo/workflows/ci/main

I'm not 100% sure how it would look. For example gg.cmd gh/cli/cli@nightly wouldn't work since the workflow name is required - but something like that.

[koppor]

Nice idea!

Quick thought: gg could GET the nightly URL and check the resulting link pointing to github.

Having #116 in mind, gg could check workflow runs on main (and master) branch and check the names of the workflow "ci", "binaries" (in my case), "check".

[eirikb]

That's actually not bad.
I agree it's lengthy, but very understandable.
In my head gh/ayn2op/discordo@main makes sene because I know gh/ will go to github and I know main isn't a version and it will check actions if no release found.
But for others it might not be that logical, so adding workflow is not a bad idea, and it makes it future proof.

[koppor]

gh/cli/cli@v2.73.0 should select the release v2.73.0, does it?

I hope, no one will name his releases or branches starting with workflow/ 😅

Shorter could be @wr/ for workflow-run.

Maybe, @w/ is also OK, because ppl will get used to it while using gg.cmd?

[koppor]

I would need gh/JabRef/jabref/pull/13112@w/binaries

Oh, I am not sure how gg.cmd knows whether its Windows, Linux, or macOS? --> This brings me back to #116

[eirikb]

gg tries to find the correct binary based on the OS you are on, so that should work fine as long as all binaries are available (in archives or not)

[koppor]

If this really works, I can radically shorten our blog post at https://blog.jabref.org/2025/05/31/run-pr/. No need for JBang, some scripts in Java, etc. -- Assuming gg.cmd "jumps" to the repo of the fork and checks the workflows there....