Skip to content
Surge.sh pending build

[#2141] Use optionals for return values that may be null to enforce a client check #3157

Sign in to view logs

[#2141] Use optionals for return values that may be null to enforce a client check

[#2141] Use optionals for return values that may be null to enforce a client check #3157

Workflow file for this run

.github/workflows/pending.yml at 967b370
# This workflow marks a deployment to surge.sh as pending
name: Surge.sh pending build
on:
pull_request_target:
branches-ignore:
- gh-pages
jobs:
deploy:
name: Deployment status
runs-on: ubuntu-latest
env:
ACTIONS_PULL_REQUEST_HEAD: ${{ github.event.pull_request.head.sha }}
ACTIONS_PULL_REQUEST_NUMBER: ${{ github.event.number }}
GITHUB_TOKEN: ${{ github.token }}
steps:
- name: Checkout repository
uses: actions/checkout@v3
- name: Update PR checklist for surge.sh as pending
run: |
mkdir -p ./pr
./config/gh-actions/deploy.sh pending
- name: Upload artifacts
if: ${{ success() }}
uses: actions/upload-artifact@v3
with:
name: reposense-deployment-id
path: ./pr
- name: Update PR checklist for surge.sh as failure
if: ${{ failure() }}
run: ./config/gh-actions/deploy.sh failure