auto-approve-action
github-actions
| auto-approve-action | github-actions | |
|---|---|---|
| 1 | 7 | |
| 383 | 1,667 | |
| - | 0.7% | |
| 5.6 | 6.6 | |
| about 1 month ago | about 1 month ago | |
| TypeScript | TypeScript | |
| MIT License | Apache License 2.0 |
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.
auto-approve-action
-
Auto Request Changes review when the job failed using Github Action
The Github Action is forked from hmarr/auto-approve-action. The action will automatically create a Request Changes pull request review. A use case is to create a request changes review when a workflow job failed.
github-actions
- On April 4, 2022 GitHub Action will force you to use "main" instead of "master" branch
-
On 2022-04-05, the default branch will be renamed from “master” to “main”
Aha: it's because the project team merged this change that intentionally fails the build when people have pinned their workflows to use the deprecated branch name: https://github.com/google-github-actions/setup-gcloud/pull/5...
(that makes sense; there has been a warning in place for a long time, and pinning to a name can be risky when the content within that reference may change over time)
-
Learning Journal 2: Brainstorm a deployment process from GitHub to Google App Engine and Cloud SQL (Part 1)
In the process of finding the answer, I discovered that the small actions are pretty much open-source. I can also go directly to their respective code repositories and learn about them. To run gsutil, I will need a setup-gcloud action.
-
Build an Uptime Monitoring System in Ruby with GCE, Cloud Storage, and PubSub
Like many aspects of the cloud, there are many ways to achieve the same result, but modern software engineering encourages CI/CD processes for several good reasons. As such, we will focus on deploying our service from Github Actions using setup-gcloud
- How to deploy Cloud Functions with GitHub Actions
-
GitOps on Kubernetes - The easy way
GKE_SA_KEY: The service account used for the project with the Base64 encoded JSON service account key. More info available here
What are some alternatives?
actions-toolkit - 🛠 A toolkit for building GitHub Actions in Node.js
wait-for-jobs - Wait for the specified jobs in the same run to be complete successfully before proceeding, helpful to prestart the job
auto-request-changes-action - 👍 GitHub Action for automatically request changes GitHub pull requests
devops-toolkit
FTP-Deploy-Action - Deploys a GitHub project to a FTP server using GitHub actions
deploy-appengine - A GitHub Action that deploys source code to Google App Engine.
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.
flow - 🌊 Continuously synchronize the systems where your data lives, to the systems where you _want_ it to live, with Estuary Flow. 🌊
rubygems - Library packaging and distribution for Ruby.
blackbox_exporter - Blackbox prober exporter
actions-cloud-functions
Hugo - The world’s fastest framework for building websites.