openrewrite / openrewrite/rewrite-github-actions
Recipe to start using Github Actions
Open
Nobody has claimed this yet.
recipe
- Dominant language
- Java
- Stars
- 1
- Forks
- 9
- Avg merge
- 5h 27m
- Merged PRs (30d)
- 12
Description
What problem are you trying to solve?
Provide an easy to use (possibly no args) recipe to do everything it takes to start using Github Actions for CI:
- a basic daily workflow for the default branch
- a PR checker workflow for all the PRs
The recipe should detect the build tool itself and apply some sane defaults.
Describe the situation before applying the recipe
- nothing in particular, or maybe no Github Actions workflows existing
Describe the situation after applying the recipe
- One or two basic Github Actions workflows
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by mapping the repository's recipe structure and build-tool handling, then define how the recipe should generate daily and pull-request workflows. Done means a no- or low-argument recipe detects the build tool and produces one or two basic GitHub Actions workflows.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100