Move to GitHub actions for all build related steps
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 4.5k
- Forks
- 884
- PR merge metrics
- No merged PRs in 30d
Description
With #1759, GitHub actions, Travis, and appveyor are all used to build and test phinx in different aspects. Given that GitHub actions supports Windows and any functionality of Travis (beyond debugging builds, which it does not seem like phinx uses), it feels like it would make sense to move everything to one build environment, and phase out the others, making it also easier to just maintain build environments going forward.
I believe looking at cakephp/cakephp that a reason to keep Travis and GH actions was for codecov, but it seems like https://github.com/codecov/codecov-action would indicate that is not necessary.
Assuming there's buy-in from the cakephp folks, I'd be happy to take this on (as I move everything else I work on to GH actions over Travis these days).
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
Inspect the repository's existing GitHub Actions, Travis, and AppVeyor build configurations, then compare the build and test responsibilities across them. Check how codecov is currently handled and review the linked CakePHP approach. Done means the build-related steps run through GitHub Actions and the other services can be phased out without losing coverage or platform support.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, php
- Domain
- build-system, ci-cd
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100