`release-action` #2

This only runs on tags that include this file, so it won't run on any upstream tags, but only on tags into which this has been merged/cherry-picked.

We plan to keep this fork alive for a significant amount of time, because it will hold an extra feature (#1) that upstream doesn't have. Automate keeping up to date with upstream to reduce our overhead. The scheme I chose for this is a little bit convoluted. There are three branches involved, but this means that the patch that we might potentially upstream is clean. Also, this scheme can't fix merge conflicts automatically, but it can find and email about them automatically, which is about as good as we can hope for.

fetching the latest tag with --depth 1 fails: that makes a shallow commit (aka a 'grafted' commit) and github refuses to accept it when being pushed back. Instead, use --shallow-exclude=HEAD which seems to get enough of the history without getting *all* of the history that github will accept the upload

We need a special token, given to us by tibdex/github-app-token, because the default token that workflows are given is constrained: > When you use the repository's GITHUB_TOKEN to perform tasks, events > triggered by the GITHUB_TOKEN will not create a new workflow run. > This prevents you from accidentally creating recursive workflow runs. > For example, if a workflow run pushes code using the repository's > GITHUB_TOKEN, a new workflow will not run even when the repository > contains a workflow configured to run when push events occur. - https://docs.github.com/en/actions/security-guides/automatic-token-authentication#using-the-github_token-in-a-workflow See also https://github.community/t/push-from-workflow-not-doesnt-trigger-on-push-tags-workflow/149151/2 GitHub recommends https://docs.github.com/en/actions/using-workflows/reusing-workflows#calling-a-reusable-workflow for solving this, but that seems a lot less flexible to me. I'd rather be able to choose whether to trigger a build by pushing a tag manually or having the bot do it.

Fixes this failure: https://github.com/neuropoly/gitea/runs/7042433953?check_suite_focus=true Also, expand the comments, now that I understand this better.

For us, as a fork working on our own bubble, these are useful

Fixes the warning from https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

This is re https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/

Gitea's official builds have this disabled. I'm not sure why. But I would like to use it at least on some neurogitea systems, so turn it on. See https://docs.gitea.io/en-us/authentication/#pam-pluggable-authentication-module

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

`release-action` #2

`release-action` #2

Commits on Nov 14, 2023

release-action #2

Are you sure you want to change the base?

release-action #2

Commits on Nov 14, 2023

`release-action` #2

`release-action` #2