actions/docker-attest-build-provenance
1
0
Fork 0
mirror of https://github.com/actions/attest-build-provenance.git synced 2026-06-13 18:19:53 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Merge 3b09a7a8af into bdd51370e0

Browse Source
This commit is contained in:
Ashleymcmillan1 2024-06-22 05:02:51 -04:00 committed by GitHub
commit 5c57bce649
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 17 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
Readme.md Normal file
View File

@ -0,0 +1,17 @@
## Contributing
[code-of-conduct]: CODE_OF_CONDUCT.md
Hi there 👋 We are excited that you want to contribute a new workflow to this repo. By doing this you are helping people get up and running with GitHub Actions and that's cool 😎.
Contributions to this project are [released](https://help.github.com/articles/github-terms-of-service/#6-contributions-under-repository-license) to the public under the [project's open source license](https://github.com/actions/starter-workflows/blob/main/LICENSE).
Before merging a new workflow, the following requirements need to be met:
- Should be as simple as is needed for the service.
- There are many programming languages and tools out there. Right now we
have a page that allows for a really large number of workflows, so we do have to be a little choosy about what we accept. Less popular tools or languages will be accepted.
- Automation and CI workflows should send data to any 3rd party service for the purposes of installing dependencies.
- Automation and CI workflows can be dependent on a paid service or product.
Thank you