Consider switching away from Travis
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 22
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Super low priority, but I think it's good to keep a trace of it.
Last month Travis got acquired by a company known to buy companies, and then stop investing in them and just suck off their pre-existing revenue streams until they die.
SRCs:
https://news.ycombinator.com/item?id=18978251
https://news.ycombinator.com/item?id=19218036
Contributor guide
No contributing guide indexed for this repository
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 reviewing the Travis acquisition sources linked in the issue and the repository's current CI setup. Define whether a migration is warranted, choose a replacement, and document the migration scope; the issue names no files, tests, or target service.
Written by the indexing model from the issue text.
Assessment
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100