create automated pipelines that can be triggered by events or run on schedule • Popular for CI/CD • Open source repos get unlimited action runs for free • The GitHub Marketplace has a large collection of ready-to-use Actions contributed by the community
in workﬂows • Actions live in dedicated repositories with an action.yml ﬁle that deﬁnes its conﬁguration • You can combine actions from the marketplace with your own custom actions • Actions must be packaged as Docker images
jobs • Each job can have multiple steps • Steps can be either an Action or a shell script • Steps run in order and share data • Jobs run in parallel unless otherwise speciﬁed • Deﬁned in a YAML ﬁle committed to the repository • You can have several different workﬂows in the same repository
need to combine this action with others? • Do I need to use repository secrets or environment variables to conﬁgure my action? • If my action creates output that needs to be persisted, where this content goes?
• How to Create a GitHub Action to Import Posts from DEV to a Repository you Own (tutorial) ◦ https://bit.ly/38nANwc • GitHub Actions documentation ◦ https://docs.github.com/en/actions • Minicli documentation ◦ https://docs.minicli.dev • Other actions built with Minicli ◦ Dynacover: https://github.com/erikaheidi/dynacover-actions ◦ Update CONTRIBUTORS: https://github.com/minicli/action-contributors