Closed
Description
This would be helpful for e.g. getting the latest version of the Java Media driver for use with the Aeron.NET C# bindings for Aeron.
I am happy to contribute on this.
Usually such an arrangement entails giving Actions access to upload to releases, and then adding the relevant actions step.
Option 1 for permissions setup - less secure
Give actions 'write' permissions on the repository.
Option 2 for permissions setup - more secure
A user with write access to the repository creates a 'fine-grained' Personal Access Token here:
- Resource owner ->
aeron-io - Expiration -> custom -> 1 year
- Repository access -> selected repositories -> this repository
- Repository permissions -> 'Contents' -> 'Read and Write'
The generated PAT is added as a new 'repository secret' here
Add step to Release workflow
- name: Upload artifacts to Release
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} # if permissions option 1
GITHUB_TOKEN: ${{ secrets.RELEASE_GITHUB_TOKEN }} # if permissions option 2
run: gh release upload ${{ TAG NAME EXPRESSION }} [file paths...]TAG NAME EXPRESSION
- For workflow runs triggered by
releaseevent,github.event.release.tag_namewill expand to the tag name - For workflow runs triggered by
pushevent withtagsfilter,github.ref_nameshould expand to the tag name ( I am not certain, but relatively confident )
Metadata
Metadata
Assignees
Labels
No labels