Skip to content

Avoid duplicate Tool Dependeny Alerts #133

@mawosoft

Description

@mawosoft
  • First alert is created for repo updates in tracked paths. At this time, the corresponding package usually has not yet been updated.
  • Second alert is created when the package has been updated. Usually, the tracked repo paths have no changes since the first alert.

In such a case, Dependency Check should add a comment to the previous alert instead of creating a new issue (currently done manually).

Example #131, #132

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions