Nightly builds are not the current master branch 😭

[Gavin-Holt]

Nightly builds are not the current master branch 😭

[JoeKar]

Looks like this was a cron task at @zyedidia's host, calling tools/nightly-release.sh, which isn't performed any longer.
Form my perspective tools/nightly-release.sh and tools/cross-compile.sh should be adapted any way:

• use $commitID as replacement for $1 respective the unneeded shell argument of tools/nightly-release.sh
  • the resulting archive will receive the commit ID in his name by default, which makes sense for a nightly
• stay with tools/cross-compile.sh in the current directory
• binaries shouldn't be moved between these scripts and everything performed in the root of the repo; then we can call tools/nightly-release.sh directly

This would allow to use this script within a GitHub action, where hub (GitHub's git extension) can be performed too, in the "usual" cron manner.

Unfortunately there is still one important point we can't bypass alone:
These GitHub actions need a secret, which we can't read/write so far...only the repository owner/admin can do.

[zyedidia]

Sorry about that, updating the release now. I think a token may have expired. I will monitor to see if this keeps being a problem in the following days.

[Gavin-Holt]

Hi

I was hoping to try the new improved brace jumping. dmaluka kindly let me know that the PR had been merged.

However, I think the current Nightly binary is stuck, only including changes up to 1f51d0b committed on Apr 27.

I'm at work today and can't access https://github.com/zyedidia/micro/archive/refs/tags/nightly.zip which is @codeload.github.com - pesky firewalls! So I can't see the source to check if the new code is included.

Sorry I should have checked the Nightly binaries earlier.

Kind Regards Gavin Holt