Describe the bug

I'm not sure what it is

To Reproduce

Expected behavior

Screenshots

Version Information (please complete the following information):

Additional context

Describe the bug

To Reproduce

Expected behavior

Screenshots

Version Information (please complete the following information):

Additional context

Describe the bug

description of test

To Reproduce

Expected behavior

Screenshots

Version Information (please complete the following information):

Additional context

Describe the bug

To Reproduce

Expected behavior

Screenshots

Version Information (please complete the following information):

Additional context

Overview

Allow for matrices

Design or Proposal

GitHub reusable workflows don't support strategy so this post details a work around

https://github.community/t/reusable-workflow-with-strategy-matrix/205676

Caller workflow

name: Node.js CI

on:
  push:
    branches: [ main ]
  pull_request:
    branches: [ main ]

jobs:
  ci:
    uses: waldos-woof/actions-automation/.github/workflows/main.yml@main
    with: 
      versions: "[\"14.x\", \"16.x\"]"

reusable workflow

name: Node.js CI

on:
  workflow_call:
    inputs:
      versions:
        description: 'Stringified JSON object listing target Node versions'
        default: '14.x'
        required: false
        type: string

jobs:
  build:

    runs-on: ubuntu-latest

    strategy:
      matrix:
        node-version: ${{fromJson(inputs.versions)}}

    steps:
    - uses: actions/checkout@v2
    - name: Use Node.js ${{ matrix.node-version }}
      uses: actions/setup-node@v2
      with:
        node-version: ${{ matrix.node-version }}
    - run: npm ci
    - run: npm run build --if-present
    - run: npm test

Describe the bug

Checking if this thing works

To Reproduce

Expected behavior

Screenshots

Version Information (please complete the following information):

Additional context

Look into issue forms

https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository

Overview

Create a common changelog for Portal related repos.

Design or Proposal

Goals:

• Include changelog from Webportal, Accounts, Skynet-js, MySky, Skyd

It probably needs to be triggered manually, cronjob or external tags might be ineffective.

Looking online, it seems that identifying repos as git submodules might be a way to pull in the changelogs. Should be able to just pull the latest version

Describe the bug

testing zap

To Reproduce

Expected behavior

Screenshots

Version Information (please complete the following information):

Additional context

Describe the bug

To Reproduce

Expected behavior

Screenshots

Version Information (please complete the following information):

Additional context

Describe the bug

This is the org level edge case to be tested

To Reproduce

Expected behavior

Screenshots

Version Information (please complete the following information):

Additional context

Describe the bug

okay

To Reproduce

Expected behavior

Screenshots

Version Information (please complete the following information):

Additional context

Describe the bug

Insert descriptive summary here

To Reproduce

Expected behavior

Pull through to Linear

Screenshots

Version Information (please complete the following information):

Additional context

....

If you mean the composite action in this repo, that is for yarn projects, and also requires more configuration whereas I prefer to have a single action that has all the basic checks.

For npm projects, using npx is the recommended way:

https://prettier.io/docs/en/install.html

npx will use the locally-installed version of prettier if found, according to these docs.

There's also a warning that you should not run npx if you don't have it added as a package. I suggest using npm run prettier --check . to ensure we're running the locally installed version and if it's not installed it should fail until we do.

Note: If you forget to install Prettier first, npx will temporarily download the latest version. That’s not a good idea when using Prettier, because we change how code is formatted in each release! It’s important to have a locked down version of Prettier in your package.json. And it’s faster, too.

Originally posted by @kwypchlo in #8 (comment)