github-actions-typing
ocurrent
github-actions-typing | ocurrent | |
---|---|---|
4 | 2 | |
33 | 135 | |
- | 0.7% | |
8.0 | 7.1 | |
7 days ago | 3 months ago | |
Kotlin | OCaml | |
Apache License 2.0 | 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.
github-actions-typing
- GitHub Actions could be so much better
- Bring type-safety to your GitHub actions' API!
- Typing for GitHub actions
-
GitHub Actions: a New Hope in YAML Wasteland
The one thing missing from the action.yml spec is the type of each input parameter. We are currently adding this information in our repository but it would be much better if it could live in your own repository in a action-types.yml file as some nice earlly adopters already do.
ocurrent
-
GitHub Actions could be so much better
Y axis is tool selection. Positive region of axis is “use a DSL”, lower region is “use a GeneralPurposeProgrammingLanguage”
The line starts at the origin, has a SMALL positive bump, than plummets downwards near vertically.
Gets it right? Tools like ocurrent (contrasted against GH actions) [1], cdk (contrasted against TF yaml) [2]
Gets it wrong? Well, see parent post. This made me so crazy at work (where seemingly everyone has been drinking the yaml dsl koolaide) that i built a local product simulator and yaml generator for their systems because “coding” against the product was so untenable.
[1] https://github.com/ocurrent/ocurrent/blob/master/doc/example...
-
Show HN: Automation the KISS way. No YAML involved
Keep working on this. It’s a splendid idea. Would be cool to eventually have a recipe where you import the crate, then program the deploy in rust, invoking your tool which builds my-build.rs, or a proper cargo build.
The following not true apples to apples, but pretty close. Rather than another crummy stringy DSL, the ocaml community said “we want to program our CI pipelines in OCaml”. So, they created https://github.com/ocurrent/ocurrent. You build your pipeline in an incredible language—then the CI server simply invokes your pipeline code, assuming you’ve implemented a basic interface.
What are some alternatives?
github-workflows-kt - Authoring GitHub Actions workflows in Kotlin. You won't go back to YAML!
z-run - z-run -- scripting library lightweight Go-based tool
ghtool - A command-line tool for interacting with Github API with some specialized features oriented around Checks
act - Run your GitHub Actions locally 🚀
azure-pipelines-agent - Azure Pipelines Agent 🚀
cheats - cheats allows you to create interactive cheat sheets for the command line.
Concourse - Concourse is a container-based continuous thing-doer written in Go.
automate - Native bash script for automate tasks in a multiple servers
pipeline - A cloud-native Pipeline resource.
tricorder - Automation the KISS way
gitlab-ci-local - Tired of pushing to test your .gitlab-ci.yml?