urbit/.github/workflows/glob.yml

name: glob
on:
  push:
    branches:
      - 'release/next-js'
jobs:
  glob:
    runs-on: ubuntu-latest
    name: "Create and deploy a glob to ~lomlyx-lopsem-nidsut-tomdun"
    steps:
      - uses: actions/checkout@v2
        with:
          lfs: true
      - uses: ./.github/actions/glob
        with:
          ship: 'lomlyx-lopsem-nidsut-tomdun'
          credentials: ${{ secrets.JANEWAY_SERVICE_KEY }}
          ssh-sec-key: ${{ secrets.JANEWAY_SSH_SEC_KEY }}
          ssh-pub-key: ${{ secrets.JANEWAY_SSH_PUB_KEY }}
meta: stage a 'glob' GitHub workflow Adds a workflow that executes the 'glob' action on every push and pull request to the 'release/next-js' branch. (For now this is just staged to the 'jt/lacd' branch for testing.) 2020-12-19 17:10:20 +03:00			`name: glob`
			`on:`
			`push:`
			`branches:`
meta: pull in lfs files when using checkout action Some other commits have been squashed in: meta: remove user declarations for glob action This is a tricky problem. SSH needs UID 0 to exist, and intuitively it does (root), but we can't enforce that when GitHub is running our container. Specifying "USER 0:0" in the actions Dockerfile doesn't cut it. Instead it seems best to try and construct a shadow-utils setup on the underlying Docker image. meta: target glob workflow at release/next-js 2020-12-19 17:27:51 +03:00			`- 'release/next-js'`
meta: stage a 'glob' GitHub workflow Adds a workflow that executes the 'glob' action on every push and pull request to the 'release/next-js' branch. (For now this is just staged to the 'jt/lacd' branch for testing.) 2020-12-19 17:10:20 +03:00			`jobs:`
			`glob:`
			`runs-on: ubuntu-latest`
			`name: "Create and deploy a glob to ~lomlyx-lopsem-nidsut-tomdun"`
			`steps:`
			`- uses: actions/checkout@v2`
meta: pull in lfs files when using checkout action Some other commits have been squashed in: meta: remove user declarations for glob action This is a tricky problem. SSH needs UID 0 to exist, and intuitively it does (root), but we can't enforce that when GitHub is running our container. Specifying "USER 0:0" in the actions Dockerfile doesn't cut it. Instead it seems best to try and construct a shadow-utils setup on the underlying Docker image. meta: target glob workflow at release/next-js 2020-12-19 17:27:51 +03:00			`with:`
			`lfs: true`
meta: fix glob action location 2020-12-19 17:15:22 +03:00			`- uses: ./.github/actions/glob`
meta: stage a 'glob' GitHub workflow Adds a workflow that executes the 'glob' action on every push and pull request to the 'release/next-js' branch. (For now this is just staged to the 'jt/lacd' branch for testing.) 2020-12-19 17:10:20 +03:00			`with:`
meta: don't sequence glob action arguments 2020-12-19 17:14:17 +03:00			`ship: 'lomlyx-lopsem-nidsut-tomdun'`
			`credentials: ${{ secrets.JANEWAY_SERVICE_KEY }}`
			`ssh-sec-key: ${{ secrets.JANEWAY_SSH_SEC_KEY }}`
			`ssh-pub-key: ${{ secrets.JANEWAY_SSH_PUB_KEY }}`
meta: stage a 'glob' GitHub workflow Adds a workflow that executes the 'glob' action on every push and pull request to the 'release/next-js' branch. (For now this is just staged to the 'jt/lacd' branch for testing.) 2020-12-19 17:10:20 +03:00