Add nightly release

[kemingy]

• As we discussed in Extend remap feature #1133 (comment)

This action will check if it has changes compared to the last nightly release, if so, it will delete the last nightly release and create a new one.

[kemingy]

According to the GitHub trigger a workflow from a workflow, the default GITHUB_TOKEN cannot trigger another workflow. Thus it requires a personal access token.

You can follow the instructions here to generate a repository level token and save it to this repo setting with the name LYCHEE. It requires the following read/write permission:

• actions
• contents

One thing I'm not sure about is the upload-asset failure: tested on my fork repo.

[mre]

Thanks for that. Added one remark. Apart from that looks good.

[kemingy]

BTW, this will need to create a nightly release in case to get the git diff. You can trigger the nightly action manually.

[mre]

Thanks! I've created the token now and added it. Let's see if it works. Triggering a build.

[mre]

https://github.com/lycheeverse/lychee/actions/runs/5842853562

[mre]

First build worked. Second build failed: https://github.com/lycheeverse/lychee/actions/runs/5842863869/job/15844411326

[kemingy]

Hi @mre, this nightly trigger has two runs:

1. Manually triggered workflow_dispatch: will create a release with the provided tag, but doesn't delete if the tag already exists (I created this one only for debugging and running the first time purpose)
2. Scheduled at 8:45 UTC: will check if there are any new commits comparing the previous nightly to the current HEAD. If so, will try to delete the previous nightly release and create a new one.

The second one will be mainly used for the nightly release. We don't need to manually trigger it anymore.

I'll keep an eye on the recent changes to see if the nightly release can work as expected.

[mre]

Thanks for the help with this.
Two more things I've wondered about:

• shall we mention the git commit somewhere in the release that the nightly is based on? Either in the release notes or the asset names?
• shall we create the binary assets as well? Right now it's just the tar archive of the source.

[kemingy]

* shall we mention the git commit somewhere in the release that the nightly is based on? Either in the release notes or the asset names?

* shall we create the binary assets as well? Right now it's just the tar archive of the source.

1. Yes I add the gh release create nightly --generate-notes so it will generate the notes automatically like https://github.com/lycheeverse/lychee/releases/tag/nightly
2. Yes it will upload the binary assets, I think it's still in progress https://github.com/lycheeverse/lychee/actions/runs/5846357265

[mre]

Awesome work! Looks nice. 👌