wflow
combine-prs-workflow
| wflow | combine-prs-workflow | |
|---|---|---|
| 1 | 3 | |
| 192 | 288 | |
| - | -0.3% | |
| 0.0 | 2.1 | |
| over 3 years ago | 9 months ago | |
| 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.
wflow
-
Awesome GitHub Actions
Not sure how “curated” this list is. The first one that caught my eye (https://github.com/phishy/wflow) has a “this repo is archived” warning with no updates since 2019.
combine-prs-workflow
-
Keeping dependencies in your GitHub projects up-to-date with Dependabot
To address inefficiency caused by separate PRs, a workflow was designed to join them automatically into one big PR. However, it was unable to deal with lockfile conflicts. PRs that caused conflict in the Combine PRs job, were omitted and you had to add them manually anyway. It spared some time, but the developer experience was still far from being perfect.
-
GitHub Actions Pitfalls
Another pitfall I ran into recently with a workflow I've been working on [1]: Checks and CI that are made with GitHub Actions are reported to the new Checks API, while some (all?) external services report to their old Statuses API. This makes it needlessly difficult to ascertain whether a PR/branch is "green" or not. They finally decided to create a "statusRollUp" that combines the state of the two APIs, but it's not available in their REST api, only their GraphQL API.
[1] https://github.com/hrvey/combine-prs-workflow/
-
Awesome GitHub Actions
GitHub Actions can do some neat things. I got tired of waiting for Dependabot (tool that makes automatic PRs to update your middleware, acquired by GitHub) to add an option to group PRs together (it opens a separate PR for each dependency that can be updated, so merging and re-running CI can take a long time) so I scratched my own itch and made a workflow that merges their PRs together: https://github.com/hrvey/combine-prs-workflow Been running it for a year now, and still pretty happy with it.
What are some alternatives?
jira-ci-cd-integration - Jira Integation for sending Build/Deploy information. Use with any CI/CD provider (via Docker)
runner-images - GitHub Actions runner images
vitemadose - Détection de créneaux de vaccination disponibles pour l'outil ViteMaDose
actionlint - :octocat: Static checker for GitHub Actions workflow files
Teedy - Lightweight document management system packed with all the features you can expect from big expensive solutions
act - Run your GitHub Actions locally 🚀
changed-files - :octocat: Github action to retrieve all (added, copied, modified, deleted, renamed, type changed, unmerged, unknown) files and directories.
jira-grafana-json-datasource - Connect Grafana to Jira cloud to retrieve metrics on your Jira issues.
gh-valet - Valet helps facilitate the migration of Azure DevOps, CircleCI, GitLab CI, Jenkins, and Travis CI pipelines to GitHub Actions.
nix-github-actions - An example project showing how to use Nix to replace third-party GitHub Actions
paths-filter - Conditionally run actions based on files modified by PR, feature branch or pushed commits