openrewrite / openrewrite/rewrite-github-actions
Composite recipe to migrate off 3rd party actions to official ones and the latest versions
Open
Nobody has claimed this yet.
enhancement
recipe
- Dominant language
- Java
- Stars
- 1
- Forks
- 9
- Avg merge
- 5h 27m
- Merged PRs (30d)
- 12
Description
What problem are you trying to solve?
Over the years you can easily end up using a big soup of 3rd party actions in some old versions. These days a lot of the functionality is provided by 1st party actions from GitHub themselves.
Describe the solution you'd like
Devise a recipe which:
- migrates known cases of replacements, e.g. MigrateTibdexGitHubAppTokenToActions
- upgrades to the latest major version of the official actions
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
Start by locating the existing MigrateTibdexGitHubAppTokenToActions recipe and the surrounding GitHub Actions recipe definitions. Review how replacement migrations and action-version upgrades are represented, then identify the relevant tests or fixtures. Done means the composite recipe covers the known replacements and upgrades supported official actions to their latest major versions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, java
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100