Kristof Mattei
Kristof Mattei
Another example: ``` # yaml-language-server: $schema=https://json.schemastore.org/github-workflow.json name: Something on: pull_request: branches: - main jobs: job1: name: Job1 runs-on: ubuntu-latest outputs: code: ${{ steps.filter.outputs.code }} steps: - name: Checkout uses: actions/checkout@v3...
This works: ``` module.exports = { client: { name: "default", localSchemaFile: './src/schema.graphql' }, }; ```
@jrconlin thanks for the response. I'm offering my bandwidth. I propose to have 3 images, spanner, mysql and the utils one. That way we can actually use a `bleeding-edge` label...
> Hmm sorry some of the tests are failing, from the looks of it, it is most likely related to #857. Could you have a look? I'm sorry this is...
@gr2m it now works on my machine!
@babblebey long overdue... > Noting the introduction of the new successCommentCondition (in https://github.com/semantic-release/github/pull/874) which accepts condition via config that results to a boolean value declaring whether both successComment and releasedLabel...
I have the same issue, going from 4.0.4 to 4.0.5: https://github.com/actions-rs-plus/clippy-check/pull/1751
> I'd sugguest to use tag (instead of different image) and add README, like: > > 1. "mozilla/syncstorage-rs:0.14.4" aka "mozilla/syncstorage-rs:0.14.4-spanner" > 2. "mozilla/syncstorage-rs:0.14.4-mysql" > 3. "mozilla/syncstorage-rs:0.14.4-tools" Unfortunately that doesn't fit...
> > Unfortunately that doesn't fit Docker's treatment of tags. > > I don't think that is accurate. It is actually quite common to distinguish different configurations of an image...