The GitHub copies of this repo's releases have never had files. github-release needed only publish, so it started alongside files and copied the Gitea release before files had attached the tarball and SHA256SUMS. It now needs files as well.
If files fails, the copy is skipped, not made empty; re-running the failed jobs makes both. actionlint reports the same findings before and after (existing shellcheck notes only).
The copies already on GitHub keep no files; they get them separately.
The GitHub copies of this repo's releases have never had files. `github-release` needed only `publish`, so it started alongside `files` and copied the Gitea release before `files` had attached the tarball and SHA256SUMS. It now needs `files` as well.
If `files` fails, the copy is skipped, not made empty; re-running the failed jobs makes both. actionlint reports the same findings before and after (existing shellcheck notes only).
The copies already on GitHub keep no files; they get them separately.
github-release needed only publish, so it ran beside files and copied
the Gitea release before files had attached the tarball and SHA256SUMS.
Every GitHub copy of a release had no files. It now needs files too.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The GitHub copies of this repo's releases have never had files.
github-releaseneeded onlypublish, so it started alongsidefilesand copied the Gitea release beforefileshad attached the tarball and SHA256SUMS. It now needsfilesas well.If
filesfails, the copy is skipped, not made empty; re-running the failed jobs makes both. actionlint reports the same findings before and after (existing shellcheck notes only).The copies already on GitHub keep no files; they get them separately.