wait-for-secrets
github-pages-deploy-action
wait-for-secrets | github-pages-deploy-action | |
---|---|---|
4 | 10 | |
273 | 4,087 | |
2.2% | - | |
0.0 | 8.6 | |
10 months ago | 8 days 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
github-pages-deploy-action
-
Setting up a free & production-ready web app backend in Go (with database) in less than 100 lines
The interesting part is towards the bottom where we build the frontend code and make use of the github-pages-deploy-action step to automatically make a new commit with the compiled frontend code to a gh-pages branch.
-
How to publish React App (CRA) on Github Pages using Github Actions with Turborepo
Finally, will do the deploy on github pages using the scripts from JamesIves/github-pages-deploy-action, and create a branch gh-pages with the code from apps/web/build.
-
Noob question regarding hosting TS apps
- Deploy to GitHub Pages using GitHub Actions
-
How to deploy and publish to NPM your own React Components library
For Storybook deploy, we will use github-pages-deploy-action
- GitHub - JamesIves/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.
-
How do you use Jinja with Github?
If you've built a site that can be rendered statically, then you can probably set up a GitHub Pages deploy via GitHub Actions (since Pages supports only Jekyll by default, you need this for any other static site generator). But if you have a server component, then you'll need to host it some other way.
-
Deploying to GitHub Pages using GitHub Actions
Around three years ago I created the github-pages-deploy-action project as my first real venture into the world of open source. I built this action so I could make continued updates to a blog while being away from my work laptop. The community response has been fantastic and I'm very happy with how it has evolved over the years as a result. I even had the opportunity to be interviewed by GitHub for my involvement back in 2020 which you can read here.
-
Using GitHub Actions to Publish Doxygen Docs to GitHub Pages
This action is a composite action using shell scripts for installing necessary tools and preparing docs and makes use of JamesIves/github-pages-deploy-action for deploying the docs to a GitHub Pages branch.
-
Deploy NextJS app to GitHub Pages using GitHub Actions
github-pages-deploy-action is used to push a static exported site to gh-pages branch.
-
Hosting Kotlin/JS on GitHub Pages via GitHub Actions
Lastly, we use another Action to deploy our project to GitHub Pages – but only if the workflow is running on the master or main branch (we don't want development branches to be deployed to the public!). We point this action to the build/distributions folder, which is where building a Kotlin/JS project creates the final .js and .html artifacts.
What are some alternatives?
FTP-Deploy-Action - Deploys a GitHub project to a FTP server using GitHub actions
actions-gh-pages - GitHub Actions for GitHub Pages 🚀 Deploy static files and publish your site easily. Static-Site-Generators-friendly.
pr-compliance-action - Check PR for compliance on title, linked issues, and files changed
tauri-action - Build your Web application as a Tauri binary for macOS, Linux and Windows
terraform-aws-oidc-github - Terraform module to configure GitHub Actions as an IAM OIDC identity provider in AWS.
action-update-file - Update (i.e. commit and push) files on GitHub
circleci-audit
ledokku - Beautiful web UI for all things Dokku
github-app-token - Impersonate a GitHub App in a GitHub Action
image-actions - A Github Action that automatically compresses JPEGs, PNGs and WebPs in Pull Requests.
jira-ci-cd-integration - Jira Integation for sending Build/Deploy information. Use with any CI/CD provider (via Docker)
aws-lambda-code-signing-action - GitHub action which uses AWS Code Signer to sign ✍🏼 AWS Lambda artifacts 📦 from your pipeline