Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The Apache Daffodil project is taking steps to enable Automated Release Signing. For part of this we developed a GitHub action workflow that we plan to use for our different Daffdil projects. But we realized this is actually pretty generic and could possibly be useful for other ASF projects. It is a little opinionated on how things should be organized, but I think what it does isn't too controversial based on what I've seen of other ASF projects, at least for some of the smaller less complex ones.
So I thought I would document it better and see if this is something that would be of interest the the ASF community.
Also note that this action will not work as-is since the .js files need to be be compiled and those compiled files committed for GitHub actions to be able to actually use them. That adds a lot of noise to the PR so I left that off.
Thoughts?