Document the timeout extension for commissioning Thread device into Thread network #18
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
# this workflow requires to provide JIRA webhook URL via JIRA_URL GitHub Secret | |
# read more: https://support.atlassian.com/cloud-automation/docs/jira-automation-triggers/#Automationtriggers-Incomingwebhook | |
# original code source: https://github.com/beliaev-maksim/github-to-jira-automation | |
name: Issues to JIRA | |
on: | |
issues: | |
# available via github.event.action | |
types: [opened, reopened, closed] | |
jobs: | |
update: | |
name: Update Issue | |
runs-on: ubuntu-latest | |
steps: | |
- name: Create JIRA ticket | |
env: | |
# put into env vars to properly escape special bash chars | |
ISSUE_TITLE: ${{ github.event.issue.title }} | |
ISSUE_DESCRIPTION: ${{ github.event.issue.body }} | |
run: | | |
# Determine Bug/Enhancement | |
if ${{ contains(github.event.*.labels.*.name, 'Bug') }}; then | |
type=bug | |
else | |
type=task | |
fi | |
# send JIRA request | |
# canonical doesn't encourage discussions in JIRA on pulic project issues. | |
# thus, it is NOT recommended to put description in JIRA in order to push conversation to GitHub | |
# if strongly required, then replace '--arg body ""' with the next line | |
# --arg body "$ISSUE_DESCRIPTION" | |
data=$( jq -n \ | |
--arg title "$ISSUE_TITLE" \ | |
--arg url '${{ github.event.issue.html_url }}' \ | |
--arg submitter '${{ github.event.issue.user.login }}' \ | |
--arg body "" \ | |
--arg type "$type" \ | |
--arg action '${{ github.event.action }}' \ | |
'{title: $title, url: $url, submitter: $submitter, body: $body, type: $type, action: $action}' ) | |
curl -X POST -H 'Content-type: application/json' --data "${data}" "${{ secrets.JIRA_URL }}" |