Create meeting notes for sig-providers #21 #1606
Workflow file for this run
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
name: wip | ||
on: | ||
pull_request: | ||
types: | ||
- opened | ||
- edited | ||
- labeled | ||
- unlabeled | ||
- synchronize | ||
jobs: | ||
wip: | ||
runs-on: ubuntu-latest | ||
steps: | ||
- uses: wow-actions/wip@v1 | ||
with: | ||
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} | ||
# Set action to failed when wip. | ||
setFailed: true | ||
# Match with PR labels. Comma separated and case insensitive labels. | ||
labels: 'do-not-merge', 'work in progress', 'wip', 'rfc', '🚧' | ||
# Match with PR title. Comma separated and case insensitive keywords. | ||
keywords: 'do-not-merge', 'work in progress', 'wip', 'rfc', '🚧' | ||
# A string label to differentiate this status from the status of | ||
# other systems. This field is case-insensitive. | ||
# @see: https://docs.github.com/en/rest/reference/repos#create-a-commit-status | ||
context: WIP | ||
# The target URL to associate with this status. This URL will be | ||
# linked from the GitHub UI to allow users to easily see the source | ||
# of the status. For example, if your continuous integration system | ||
# is posting build status, you would want to provide the deep link | ||
# for the build output for this specific SHA: http://ci.example.com/user/repo/build/sha | ||
# @see: https://docs.github.com/en/rest/reference/repos#create-a-commit-status | ||
target_url: '' | ||
# A short description of the status. | ||
# @see: https://docs.github.com/en/rest/reference/repos#create-a-commit-status | ||
wip_description: 'work in progress' | ||
ready_description: 'ready for review' |