Github reporting module creates a new issue everytime for the same finding

[monishbb]

Nuclei version:

3.2.9

Current Behavior:

Using update-existing in Github reporting module does not work, it still creates a new issue for an already existing issue

allow-list:
  severity: info, low, high, critical, medium

# GitHub contains configuration options for GitHub issue tracker
github:
  # issue-label is the label of the created issue type
  issue-label: security
  # update-existing is the boolean which tells if the existing, opened issue should be updated or new one should be created
  update-existing: true
  # duplicate-issue-check flag to enable duplicate tracking issue check.
  duplicate-issue-check: true
  # username of the github accont being used
  username: test-user
  # token is the token for GitLab account
  token: test-token
  # project-name is the name/id of the project(repository)
  project-name: "1234"

Expected Behavior:

Existing issues on Github should have been updated instead of a new issue being created

Steps To Reproduce:

1. Use https://github.com/projectdiscovery/nuclei-action
2. Pass the above report config:

- name: Nuclei - Vulnerability Scan
          uses: projectdiscovery/nuclei-action@main
          with:
            target: https://www.example.com
            github-report: true
            github-token: ${{ github.token }}
            report-config: vapt-config/nuclei-reporting.yaml
            config: vapt-config/nuclei-config.yaml
            flags: -disable-unsigned-templates

3. Multiple issues are created for the same findings if run multiple times

Anything else:

#3429
projectdiscovery/nuclei-action#60

[dogancanbakir]

It should be duplicate-issue-check: true https://github.com/projectdiscovery/nuclei/blob/dev/cmd/nuclei/issue-tracker-config.yaml#L35 instead of update-existing: true. Example config,

and result