[Schema Inaccuracy] "Content Tree" content is a required property, but is unlisted #17
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
| # When the `documentation` label is added for documentation issues, | |
| # this workflow copies the issue to the API team repo which can then | |
| # be transferred to the feature team that owns the problem endpoint | |
| # so they can resolve the documentation problem | |
| # (we do not transfer the original issue so that the issue does not disappear for the contributor) | |
| name: Copy documentation issue | |
| on: | |
| issues: | |
| types: | |
| - labeled | |
| jobs: | |
| copy-issue: | |
| name: Copy documentation issue | |
| runs-on: ubuntu-latest | |
| if: github.event.label.name == 'documentation' | |
| steps: | |
| - name: priority | |
| uses: actions/github-script@626af12fe9a53dc2972b48385e7fe7dec79145c9 | |
| id: priority | |
| with: | |
| result-encoding: string | |
| script: | | |
| const labels = context.payload.issue.labels; | |
| let priority = "unknown" | |
| for (const label of labels) { | |
| if (['P1','P2','P3','P4'].includes(label.name)){ | |
| priority = label.name | |
| break | |
| } | |
| } | |
| return priority | |
| - name: Create an issue in the api-platform repo | |
| run: | | |
| new_issue_url="$(gh issue create --title "$ISSUE_TITLE" --body "$ISSUE_BODY" --repo github/api-platform --label "REST,openapi")" | |
| echo 'NEW_ISSUE='$new_issue_url >> $GITHUB_ENV | |
| env: | |
| GITHUB_TOKEN: ${{secrets.ISSUE_TRANSFER_TOKEN}} | |
| ISSUE_TITLE: ${{ github.event.issue.title }} | |
| ISSUE_BODY: ${{ github.event.issue.body }} | |
| - name: Comment on the new issue | |
| run: | | |
| gh issue comment $NEW_ISSUE --body "This issue was originally opened in the rest-api-description repo as $OLD_ISSUE with priority $PRIORITY on a scale of P1 (high) to P4 (low). Please transfer it to the appropriate feature team. | |
| :exclamation: When you close this issue, also comment on and close the original issue. | |
| :question: Was this issue something that could have been caught by a linter? If so, suggest a new rule in [#api-platform](https://github.slack.com/archives/C1042T6MS)." | |
| env: | |
| GITHUB_TOKEN: ${{secrets.ISSUE_TRANSFER_TOKEN}} | |
| NEW_ISSUE: ${{ env.NEW_ISSUE }} | |
| OLD_ISSUE: ${{ github.event.issue.html_url }} | |
| PRIORITY: ${{ steps.priority.outputs.result }} |