-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide artifacts upload tool as GHA #12
Comments
Since we have a public |
I thought of putting the actions in this repository (once it's made public, of course) because release-engineering owns it. I don't know who owns https://github.com/paritytech/actions. Do we have a strong preference for the |
I think it would be good to have ALL GHA (not only about releases) in one repo and |
See #17 |
We can follow up the topic here: paritytech/actions#2 |
As explained in https://github.com/paritytech/release-engineering/issues/102#issuecomment-1308414160
Since we intend to have multiple scripts in the repository, it's necessary to think about how to provide them as GitHub Actions. One approach would be to have multiple
action.yml
in a single repository for each entrypoint, as done by e.g. https://github.com/github/codeql-action/blob/73ff862014865b27593070d3b63161a0012a39ec/analyze/action.yml#L80 (see https://github.com/orgs/community/discussions/24990 and https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#example-using-a-public-action-in-a-subdirectory). Thus the usage would be:The text was updated successfully, but these errors were encountered: