Real-Time Notification Update Bug in Chat Functionality #577
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: GitHub Issue Sync | |
| on: | |
| issues: | |
| types: | |
| - opened | |
| - labeled | |
| workflow_dispatch: | |
| inputs: | |
| excludeClosed: | |
| description: 'Exclude closed issues in the sync.' | |
| type: boolean | |
| default: true | |
| jobs: | |
| sync: | |
| runs-on: ubuntu-latest | |
| steps: | |
| - name: Sync issues | |
| uses: paritytech/github-issue-sync@master | |
| with: | |
| # This token is autogenerated by GitHub | |
| GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} | |
| # This is a Personal Access Token and it needs to have the following permissions | |
| # - "read:org": used to read the project's board | |
| # - "write:org": used to assign issues to the project's board | |
| PROJECT_TOKEN: ${{ secrets.PROJECT_TOKEN }} | |
| # The number of the project which the issues will be synced to | |
| # You can find this in https://github.com/orgs/@ORGANIZATION/projects/<NUMBER> | |
| project: 1 | |
| # Optional, the project field to modify with a new value | |
| # Found more in https://docs.github.com/en/issues/planning-and-tracking-with-projects/understanding-fields/about-single-select-fields | |
| project_field: Status | |
| # Optional unless that project_field was set up. Then this field is required. | |
| # The value to modify in the project field | |
| project_value: Backlog | |
| # Optional, labels to work with. Read below to see how to configure it. | |
| # If this value is set, the action will be applied only to issues with such label(s). | |
| labels: | | |
| task |