Duplicate GitHub issues prevention #60

New issue

Closed

opened 2023-06-19 09:23:13 -04:00 by rotemreiss · 4 comments

rotemreiss commented

2023-06-19 09:23:13 -04:00

(Migrated from github.com)

I'm using the action with custom templates and the option to report findings as GitHub issues.
The issue is that every time my workflow runs (e.g., on push) new issues on the same findings are being created.
Is it possible to not open new issues if an issue already exists? If not, this should only be used on releaae, or what is the optimal trigger for such a workflow?

I'm using the action with custom templates and the option to report findings as GitHub issues. The issue is that every time my workflow runs (e.g., on push) new issues on the same findings are being created. Is it possible to not open new issues if an issue already exists? If not, this should only be used on releaae, or what is the optimal trigger for such a workflow?

forgedhallpass commented

2023-06-19 17:07:37 -04:00

(Migrated from github.com)

I've created a ticket that would cover this. You can track it here:
https://github.com/projectdiscovery/nuclei/issues/3429

I've created a ticket that would cover this. You can track it here: https://github.com/projectdiscovery/nuclei/issues/3429

👀 2

dogancanbakir commented

2024-02-27 07:38:42 -05:00

(Migrated from github.com)

Closing this since this feature is now available for use.

monizb commented

2024-07-01 07:15:57 -04:00

(Migrated from github.com)

@dogancanbakir I tried using this on my repo and setting update-existing to true under github, it still seems to create a new issue for every existing issue, here is my reporting config:

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: user
  # token is the token for GitLab account
  token: test-token
  # project-name is the name/id of the project(repository)
  project-name: "1234"

@dogancanbakir I tried using this on my repo and setting update-existing to true under github, it still seems to create a new issue for every existing issue, here is my reporting config: ``` 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: user # token is the token for GitLab account token: test-token # project-name is the name/id of the project(repository) project-name: "1234" ```

dogancanbakir commented

2024-07-01 07:19:20 -04:00

(Migrated from github.com)

@monizb, Can you create a new issue on http://github.com/projectdiscovery/nuclei ? Thanks!

👍 1

No labels

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

projectdiscovery/nuclei-action#60

No description provided.

Rows
Columns