Don't create checks on issues about toolkit

[gimenete]

@damccorm I'll create an internal issue. The problem is that when an event not related to a push triggers Actions, Actions searches the latest version of the workflow files. In order to do that it uses the latest commit in the default branch. This makes sense in order to decide which version of the workflow file is used. Then checks are created and the SHA is stored in them. These checks need to be created to show up in the Actions tab and be able to debug anything.

However that SHA used to find the right workflow file version may also be the latest SHA in a PR, which causes the checks to appear in the merge box (and probably other places of the UI) and this is what's happening here, which is confusing to the users.

[damccorm]

@gimenete actions/stale#13 looks like the same issue

[estrada9166]

I have this workflow

name: "Issue assigner"

on: [issues, issue_comment]

jobs:
  triage:
    runs-on: ubuntu-latest
    steps:
    - name: Issue assigner
      if: github.event.action == 'created' || github.event.action == 'opened'
      uses: estrada9166/issue-assigner@v1
      with:
        GITHUB_TOKEN: "${{ secrets.GITHUB_TOKEN }}"
        WITH_COMMENTS: true

[gimenete]

We have shipped a fix for this. Here's a blog post with more information https://github.blog/changelog/2019-09-24-ui-changes-in-github-actions-checks/

[damccorm]

What are you triggering your workflow on? In theory on: issues should have this behavior and shouldn't create any checks

[damccorm]

@gimenete you did some work on checks right? This looks like unexpected behavior to me, could you take a look (or repath to someone better)?

[bryanmacfarlane]

Closing here since not toolkit related and tracking internally