Docs: replace Travis CI example with GitHub Actions

Open
#370 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
42/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
github-actions

Research direction

Start by locating the documentation containing the linked Travis CI example, then compare it with the referenced GitHub Actions gist. Done means the Travis CI case is replaced by an accurate GitHub Actions example while the related documentation remains coherent.

Written by the indexing model from the issue text.

Description

It is probably a good idea to replace the Travis CI case with GitHub Actions - example

Related

  • #215
  • #216
Dominant language
JavaScript
Stars
339
Forks
75
Avg merge
5h 15m
Merged PRs (30d)
6

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from semantic-release/git

All issues in semantic-release/git

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.