Skip to content

Commit

Permalink
chore: switch from Travis CI to GitHub Actions
Browse files Browse the repository at this point in the history
  • Loading branch information
bmish committed Jun 11, 2020
1 parent 5052f7d commit dd0d56d
Show file tree
Hide file tree
Showing 3 changed files with 38 additions and 31 deletions.
28 changes: 28 additions & 0 deletions .github/workflows/ci.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,28 @@
# This workflow will do a clean install of node dependencies, build the source code and run tests across different versions of node
# For more information see: https://help.github.com/actions/language-and-framework-guides/using-nodejs-with-github-actions

name: CI

on:
push:
branches: [ master ]
pull_request:
branches: [ master ]

jobs:
build:

runs-on: ubuntu-latest

strategy:
matrix:
node-version: [8.x, 10.x, 12.x, 14.x]

steps:
- uses: actions/checkout@v2
- name: Use Node.js ${{ matrix.node-version }}
uses: actions/setup-node@v1
with:
node-version: ${{ matrix.node-version }}
- run: yarn install --frozen-lockfile --non-interactive
- run: yarn test
25 changes: 0 additions & 25 deletions .travis.yml

This file was deleted.

16 changes: 10 additions & 6 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# find-yarn-workspace-root

[![Build Status](https://travis-ci.org/square/find-yarn-workspace-root.svg?branch=master)](https://travis-ci.org/square/find-yarn-workspace-root)
![CI](https://github.com/square/find-yarn-workspace-root/workflows/CI/badge.svg)

Algorithm for finding the root of a yarn workspace, extracted from yarnpkg.com

Expand Down Expand Up @@ -40,13 +40,17 @@ Then create a branch for your bugfix/feature, make changes and update the tests,
## Releases

Releases are handled by Travis CI once a build succeeds on `master`. To trigger a release, bump the version using `standard-version`:
To trigger a release, bump the version using `standard-version`:

```bash
$(yarn bin)/standard-version
```
1. To update the CHANGELOG, bump the version in `package.json`, and create a git tag, run:

```bash
$(yarn bin)/standard-version
```

2. `git push && git push --tags`

That should update the CHANGELOG, bump the version in `package.json`, and create a git tag. Then, just `git push && git push --tags`.
3. `npm publish`

---
Copyright 2017 Square, Inc.

0 comments on commit dd0d56d

Please sign in to comment.