combine-prs-workflow
actionlint
combine-prs-workflow | actionlint | |
---|---|---|
3 | 5 | |
288 | 2,361 | |
-0.3% | - | |
2.1 | 9.5 | |
9 months ago | 5 days ago | |
Go | ||
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.
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.
actionlint
-
GitHub Actions could be so much better
Yep, actionlint is great! I've used it successfully both to lint my own workflows, and to lint third-party workflows for (basic) security issues.
Unfortunately, it can't lint actions themselves, only workflows that call actions[1]. This is a substantial deficiency, especially for users (like me) who write and maintain a decent number of actions.
[1]: https://github.com/rhysd/actionlint/issues/46
-
What are the not-so-obvious tools that you don't want to miss?
I recently discovered actionlint and immediately told everyone that would listen about it. And now you are too. Static analysis for github actions, it's been pretty useful.
- Linter for GHA syntax?
-
GitHub Actions Pitfalls
The first pitfall can be statically detected with actionlint
https://github.com/rhysd/actionlint
$ actionlint oops.yaml
What are some alternatives?
runner-images - GitHub Actions runner images
changed-files - :octocat: Github action to retrieve all (added, copied, modified, deleted, renamed, type changed, unmerged, unknown) files and directories.
vitemadose - Détection de créneaux de vaccination disponibles pour l'outil ViteMaDose
gh-valet - Valet helps facilitate the migration of Azure DevOps, CircleCI, GitLab CI, Jenkins, and Travis CI pipelines to GitHub Actions.
travis-yml - Travis CI build config processing
paths-filter - Conditionally run actions based on files modified by PR, feature branch or pushed commits
just - 🤖 Just a command runner
roadmap - GitHub public roadmap