Skip to content

Commit

Permalink
💚 ci: Fixed packages not installing
Browse files Browse the repository at this point in the history
  • Loading branch information
joebobmiles committed Jul 11, 2021
1 parent d8972d1 commit c245f27
Showing 1 changed file with 18 additions and 8 deletions.
26 changes: 18 additions & 8 deletions .github/workflows/test.yml
Original file line number Diff line number Diff line change
Expand Up @@ -28,12 +28,6 @@ jobs:
# Provide a "password" to GPR so that we can pull our packages.
NODE_AUTH_TOKEN: ${{ secrets.GITHUB_TOKEN }}

- uses: actions/upload-artifact@v2
if: ${{ always() }}
with:
name: npm-error-log
path: /home/runner/.npm/_logs

- run: npx commitlint --from HEAD~1 --to HEAD --verbose

eslint:
Expand All @@ -46,7 +40,16 @@ jobs:
- uses: actions/setup-node@v2
with:
node-version: 15
registry-url: 'https://registry.npmjs.org'
# We must indicate the Github Package Registry, as our config packages
# are there (and also NPM). Frustratingly, NPM prefers the GPR over
# NPM - even when we indicate that we want to pull from NPM instead of
# the GPR.
registry-url: https://npm.pkg.github.com

- run: npm ci
env:
# Provide a "password" to GPR so that we can pull our packages.
NODE_AUTH_TOKEN: ${{ secrets.GITHUB_TOKEN }}

- run: npm ci

Expand All @@ -62,8 +65,15 @@ jobs:
- uses: actions/setup-node@v2
with:
node-version: 15
registry-url: 'https://registry.npmjs.org'
# We must indicate the Github Package Registry, as our config packages
# are there (and also NPM). Frustratingly, NPM prefers the GPR over
# NPM - even when we indicate that we want to pull from NPM instead of
# the GPR.
registry-url: https://npm.pkg.github.com

- run: npm ci
env:
# Provide a "password" to GPR so that we can pull our packages.
NODE_AUTH_TOKEN: ${{ secrets.GITHUB_TOKEN }}

- run: npm run test

0 comments on commit c245f27

Please sign in to comment.