wait-for-secrets
pr-compliance-action
| wait-for-secrets | pr-compliance-action | |
|---|---|---|
| 4 | 2 | |
| 273 | 159 | |
| 2.2% | - | |
| 0.0 | 6.5 | |
| 10 months ago | 5 months ago | |
| TypeScript | TypeScript | |
| Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
wait-for-secrets
-
How to publish on npm with `--provenance` using Lerna-Lite
To deal with the OTP (or any other 2FA), we can use wait-for-secrets. Compared to the previous basic usage, we are splitting the Lerna-Lite Version & Publish into 2 separate tasks. The reason is simple, calling the OTP too early would timeout even before reaching the publish phase, so calling the OTP just before the publish is the best way to avoid invalid pin.
-
Rotate any secrets stored in CircleCI
While OIDC is a good option, at StepSecurity, we are building an open-source project that allows using your MFA tokens for deployments in CI/ CD. So far, it is implemented for GitHub Actions - https://github.com/step-security/wait-for-secrets. In this method, you get a link in the build log, click the link, and can enter credentials at run time, which then gets used in the next step in the pipeline for deployment. So there are no persistent secrets stored in the CI/ CD pipeline and no need for managing/ rotating separate deployment credentials.
- A way to publish from GitHub Actions using multi-factor authentication
- Show HN: Publish from GitHub Actions using multi-factor authentication
pr-compliance-action
-
How to lint PRs and welcome contributors using GitHub Actions
mtfoley/[email protected] - check PR for compliance on title, linked issues, and files changed
-
pr-compliance-action
Inspired by this need of the project, and some of the work in pr-lint-action, I managed to create and do a pre-release on pr-compliance-action, and it was implemented in the Open Sauced project last week!
What are some alternatives?
FTP-Deploy-Action - Deploys a GitHub project to a FTP server using GitHub actions
first-interaction - An action for filtering pull requests and issues from first-time contributors
terraform-aws-oidc-github - Terraform module to configure GitHub Actions as an IAM OIDC identity provider in AWS.
action-semantic-pull-request - A GitHub Action that ensures that your PR title matches the Conventional Commits spec.
circleci-audit
open-sauced - 🍕 This is a project to identify your next open source contribution.
github-pages-deploy-action - 🚀 Automatically deploy your project to GitHub Pages using GitHub Actions. This action can be configured to push your production-ready code into any branch you'd like.
foundry-gas-diff - 🛠️ Easily track & compare gas costs estimated by Foundry on each of your Pull Requests!
conventional-commit - commit binary powered by commitizen with conventional commit standard
pr-lint-action - :octocat: A fast 🔥 TypeScript GitHub Action to ensure that your PR title matches a given regex.
setup-bun - Set up your GitHub Actions workflow with a specific version of Bun
mc-publish - 🚀 Your one-stop GitHub Action for seamless Minecraft project publication across various platforms.