For some reason, issues are created twice?

This is my current workflow.

Thanks!

# This is a basic workflow to help you get started with Actions

name: TODO's to issues

# Controls when the action will run. Triggers the workflow on push or pull request
# events but only for the master branch
on:
  pull_request:
    branches: [ master, staging ]

# A workflow run is made up of one or more jobs that can run sequentially or in parallel
jobs:
  build:
    runs-on: "ubuntu-latest"
    steps:
      - uses: "actions/checkout@master"
      - name: "TODO to Issue"
        uses: "alstr/todo-to-issue-action@master"
        with:
          REPO: ${{ github.repository }}
          BEFORE: ${{ github.event.before }}
          SHA: ${{ github.sha }}
          TOKEN: ${{ secrets.GITHUB_TOKEN }}
          LABEL: "@todo"
          COMMENT_MARKER: "@"
        id: "todo"

[cynthiarich]

@alstr I saw similar behavior today. Here’s some links to check it out:

• My workflow file is here running only on [push]
• I added a TODO in the same PR here
• It created the issue here and another one here

It’s possible it is picking it up the merge to master as a second commit, but I thought it was supposed to ignore it since there was already an issue opened for that comment.

It also didn’t close the issue when I removed the comment 😢

[camposcristian]

Great, thanks for the context! Attaching some logs, but not sure if they’re very relevant. Let me know if you need something specific.

logs_2363.zip logs_2358.zip

Also, I thought if we run the action on every push on staging/master, issues won’t be created again if they already exist? I could try using on: release for every time we create a new one, but if we haven’t tackled the TODO and deleted the comment it will be fired again?

Also, I notice your workflow file says Triggers the workflow on push or pull request, but you’ve only set it to run on pull_request - is that intentional?

Sorry, this was just a comment left behind 😃