With https://github.com/softprops/action-gh-release I can do on: release and then append builds to the release:
- name: Publish to Github
uses: softprops/action-gh-release@v1
with:
files: 'dist/*'
fail_on_unmatched_files: true
With actions/forgejo-release, I am not allowed to upload assets into a pre-existing release (i.e. every and any release triggered by on: release!) by default; it's expecting the releases to be made with on: push: branches: [master] I guess? To allow this, I have to use override:
- name: Publish to Codeberg
uses: actions/forgejo-release@v2
with:
direction: upload
override: true
release-dir: dist/
sha256sum: true
token: ${{ secrets.FORGEJO_TOKEN }}
but override also overrides my release notes and, I suppose, any other release assets already manually uploaded before the build finishes.
softprop's more liberal version is more flexible and easy to work with.
Is this the right forum to ask for patches to forgejo-release?
With https://github.com/softprops/action-gh-release I can do `on: release` and then append builds to the release:
```
- name: Publish to Github
uses: softprops/action-gh-release@v1
with:
files: 'dist/*'
fail_on_unmatched_files: true
```
With actions/forgejo-release, I am not allowed to upload assets into a pre-existing release (i.e. every and any release triggered by `on: release`!) by default; it's expecting the releases to be made with `on: push: branches: [master]` I guess? To allow this, I have to use `override`:
```
- name: Publish to Codeberg
uses: actions/forgejo-release@v2
with:
direction: upload
override: true
release-dir: dist/
sha256sum: true
token: ${{ secrets.FORGEJO_TOKEN }}
```
but `override` _also overrides my release notes_ and, I suppose, any other release assets already manually uploaded before the build finishes.
softprop's more liberal version is more flexible and easy to work with.
Is this the right forum to ask for patches to forgejo-release?