spec-action

Activates spec for your GitHub workflow.

Usage

The spec-action needs to have either dart or flutter on the path before it can activate spec.

With Flutter

steps:
- uses: actions/checkout@v3
- uses: subosito/flutter-action@v2
- uses: bluefireteam/spec-action@v3

With Dart

steps:
- uses: actions/checkout@v3
- uses: dart-lang/setup-dart@v1
- uses: bluefireteam/spec-action@v3

Arguments

You can set a version constraint for the spec version if you don't want the latest version (default).

Simply adding the version, like in the example below, will guarantee that exactly the specified version is activated.

You can also use all range constraints that exist for pub. For example '^1.0.0' would allow any version from 1.0.0 to 2.0.0 (but not including 2.0.0). If you want an even tighter restriction you can define the version like this '>=1.2.0 < 1.3.0' which would allow any version between 1.2.0 (included) to 1.3.0 (excluded).

steps:
- uses: actions/checkout@v3
- uses: subosito/flutter-action@v2
- uses: bluefireteam/spec-action@v3
  with:
    spec-version: '1.2.0'

By default spec is run by the action (which runs the tests), if you don't want it to run set run-tests: false.

steps:
- uses: actions/checkout@v3
- uses: subosito/flutter-action@v2
- uses: bluefireteam/spec-action@v3
  with:
    run-tests: false