Verify that the workflow doesn't have access to the specified secret.
Verify that the workflow doesn't have access to the specified secret. This can be very useful for throwing an error should a flow authored by dependabot for example have access to a secret like an iam credential.
- name: Retag an image in Amazon ECR
id: retag-ecr
uses: climatepolicyradar/gha-verify-no-secret-access@v0
with:
repository-name: example
source-tag: latest
destination-tag: release
- name: Retag an image in Amazon ECR
id: retag-ecr
uses: climatepolicyradar/[email protected]
with:
repository-name: example
source-tag: latest
destination-tag: release
Name | Description | Default | Required |
---|---|---|---|
repo_secret | The secret to verify no access for. | n/a | yes |
Update usage automatically in README.md.
make docs
Run the following command to bump up.
make bump
This command will execute the following steps:
- Update VERSION
- Update README.md
- Commit and push
- Create a pull request
- Open the web browser automatically for reviewing pull request
Then review and merge, so the release is ready to go.
Run the following command to create a new release.
make release
This command will execute the following steps:
- Push tag
- Create a new GitHub Release as a draft
- Open the web browser automatically for editing GitHub Release
Edit to publicize the GitHub Release.
- Click the edit icon on the right side of the page
- Edit the release notes
- Click
Publish release
Then, the new version are published in GitHub Marketplace. Finally, we can use the new version! 🎉
Apache 2 Licensed. See LICENSE for full details.