Issue event types documentation lacks details for several event types that can be found in the API #4358
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: Create SME review tracking issue | |
| # **What it does**: Creates an SME review tracking issue when the `needs SME` label is applied to a PR or issue | |
| # **Why we have it**: We do not want to manually create an SME review tracking issue when an SME review is needed | |
| # **Who does it impact**: Hubbers | |
| on: | |
| issues: | |
| types: | |
| - labeled | |
| # Required in lieu of `pull_request` so that this workflow can query users in org to determine membership. | |
| pull_request_target: | |
| types: | |
| - labeled | |
| permissions: | |
| contents: read | |
| jobs: | |
| create-sme-review-tracking-issue: | |
| runs-on: ubuntu-latest | |
| if: github.repository == 'github/docs' && github.event.label.name == 'needs SME' | |
| steps: | |
| - id: create-issue | |
| env: | |
| URL: ${{ github.event.pull_request.html_url || github.event.issue.html_url }} | |
| uses: actions/github-script@e69ef5462fd455e02edcaf4dd7708eda96b9eda0 | |
| with: | |
| github-token: ${{ secrets.DOCS_BOT_PAT_WORKFLOW_READORG }} | |
| script: |- | |
| const issueNo = context.number || context.issue.number | |
| // Create an issue in docs-team repo | |
| await github.rest.issues.create({ | |
| owner: 'github', | |
| repo: 'docs-team', | |
| title: `SME tracking issue for \#${issueNo}`, | |
| body: `### Issue / PR that requires an SME review | |
| ${process.env.URL} | |
| ### Reason for SME review | |
| @${context.payload.sender.login} (Optional) _Insert short answer regarding why SME assistance is required to review this contribution_ | |
| ### Location SME review was requested | |
| _Insert link to the location SME review was initially requested_ | |
| #### In the comments below, include notes regarding SME review progress (examples) - | |
| - Routed to another channel / team | |
| - Reviewer stating they'll need to get back to us at a later time | |
| - Review provided was unclear or missing key information, and a follow-up is necessary | |
| `, | |
| labels: ['on track','open source', 'sme-review'], | |
| }); |