Improving Testing & Continuous Integration in Phoenix
Open
discuss
enhancement
help wanted
T25m
technical
- Dominant language
- No language data
- Stars
- 664
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Description
This looks worth reading from a CI/CD/DevOps perspective:
https://www.phoenixframework.org/blog/improving-testing-and-continuous-integration-in-phoenix
Ultimately, we might need to adopt GitHub Actions for our Phoenix Projects.
We need to assess the complexity/benefits of migrating from Travis-CI. 💭
Contributor guide
Research direction
Start by reading the linked Phoenix blog post and reviewing the repository's existing Travis-CI configuration. Assess the complexity and benefits of migrating the Phoenix projects to GitHub Actions; done means documenting a clear recommendation and migration scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100