Quantum
branch-deploy
Quantum | branch-deploy | |
---|---|---|
6 | 1 | |
26 | 325 | |
- | 3.4% | |
9.8 | 9.4 | |
about 2 months ago | 13 days ago | |
JavaScript | JavaScript | |
MIT License | 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.
Quantum
branch-deploy
-
Do you run terraform apply before or after a merging?
Before, using the branch deploy action after also running a plan. If something goes wrong after a branch deploy I can just redeploy main and don't have to untangle any merged PRs. If everything is fine then I merge.
What are some alternatives?
kubero - A free and self-hosted Heroku PaaS alternative for Kubernetes that implements GitOps
Django_AWS_Lightsail_Template - Simple Template to deploy Django Apps to AWS Lightsail through Github Actions
coolify - An open-source & self-hostable Heroku / Netlify / Vercel alternative.
terrateam - Terraform automation for teams. Purpose-built for GitHub.
Portfolio - My portfolio website
deploy-pages - GitHub Action to publish artifacts to GitHub Pages for deployments
keepalive-workflow - GitHub action to prevent GitHub from suspending your cronjob based triggers due to repository inactivity
manual-approval - Pause your GitHub Actions workflow and request manual approval from set approvers before continuing
404-links - 🚨 | The only Github Action that will open pull request review when a broken link has been found in one of your markdown documentation.
a_repo_with_9_stars_and_0_forks - Automatic change repository name with stars and forks count after 60s