Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ci: Replace CircleCI with GitHub Actions #759

Merged
merged 24 commits into from
Jul 14, 2023
Merged
Show file tree
Hide file tree
Changes from 20 commits
Commits
Show all changes
24 commits
Select commit Hold shift + click to select a range
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
324 changes: 0 additions & 324 deletions .circleci/config.yml

This file was deleted.

53 changes: 53 additions & 0 deletions .github/workflows/deploy.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,53 @@
name: Deploy

on:
push:
branches:
- develop
- master

jobs:
stephenmathieson marked this conversation as resolved.
Show resolved Hide resolved
canary:
runs-on: ubuntu-latest
if: github.ref_name == 'develop'
steps:
- uses: actions/checkout@v3
- uses: actions/setup-node@v3
with:
node-version: 18
- uses: actions/cache@v3
stephenmathieson marked this conversation as resolved.
Show resolved Hide resolved
with:
path: '**/node_modules'
key: ${{ runner.os }}-npm-${{ hashFiles('**/package-lock.json') }}
# Make sure the working tree is clean
- run: git reset --hard HEAD
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Was this here previously for some reason that was specific to circleci? This feels like something that should be a "fail the build if not true" step, not a "silently force it to be true" step

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I do not know why this was here previously.

- run: |
npx lerna publish prepatch \
stephenmathieson marked this conversation as resolved.
Show resolved Hide resolved
--no-verify-access \
--no-git-tag-version \
--no-push \
--canary \
--dist-tag=next \
--exact \
--force-publish \
--yes

production:
runs-on: ubuntu-latest
if: github.ref_name == 'master'
steps:
- uses: actions/checkout@v3
- uses: actions/setup-node@v3
with:
node-version: 18
- uses: actions/cache@v3
with:
path: '**/node_modules'
key: ${{ runner.os }}-npm-${{ hashFiles('**/package-lock.json') }}
# Make sure the working tree is clean
- run: git reset --hard HEAD
- run: |
npx lerna publish from-package \
--force-publish='*' \
--yes
- uses: softprops/action-gh-release@v1
stephenmathieson marked this conversation as resolved.
Show resolved Hide resolved
Loading