Use GitHub Actions and delete Travis / AppVeyor configuration
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- C++
- Stars
- 3.4k
- Forks
- 531
- Avg merge
- 21m
- Merged PRs (30d)
- 1
Description
Some internal discussion suggests that we should migrate all organization repositories to GitHub Actions. As far as I am aware, this is the only remaining repository in the Node.js organization that has a Travis configuration.
This issue is not a duplicate of but likely supercedes https://github.com/nodejs/nan/issues/508.
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 this repository's Travis and AppVeyor configuration, then check whether a GitHub Actions configuration already exists. Read issue #508 for related context; done means the repository uses GitHub Actions and the obsolete Travis and AppVeyor configuration is removed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- build-system, ci-cd
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100