Assaf Attias

Our apologies for the inconvenience caused by this. This PR - [jfrog-client-js/pull/73](https://github.com/jfrog/jfrog-client-js/pull/73) should fix it. Fix released from version [2.2.0](https://github.com/jfrog/jfrog-vscode-extension/releases/tag/2.2.0)+

Hi @nitaym13 , Our apologies for the inconvenience caused by this. please try our new major update to a new feel and looks. We also have an option now to...

Hi @imranzunzani, We appreciate you bringing this issue to our attention. Regarding the error you mentioned, could you please specify the version you are currently using? We recommend performing a...

Hi @imranzunzani, Thank you for the feedback. We have incorporated your suggestion to include license violations in the GitHub security tab at the time of repository scanning in our list...

Hi @imranzunzani, We are actively working on new UI in the JFrog platform that would facilitate the Frogbot repository scan results, and later to also show PR results, violations and...

Hello everyone, @imranzunzani, As requested, we have implemented alerting for license violations on the scan repository command, in the following pull request: https://github.com/jfrog/frogbot/pull/575. This feature has been released and is...

Hi @imranzunzani, Thank you for using Frogbot! This issue is known when you have multiple projects with the same dependencies. We are actively working on fixing it and providing a...

Hi @vinodhini-devops, thank you for bringing up this issue By default, Frogbot is expected to remove all of its previous comments during a rerun and add only the current one....

Hi @vinodhini-devops, the config mentioned: `JF_AVOID_PREVIOUS_PR_COMMENTS_DELETION: TRUE` so it will not delete the old one with that, as mentioned can you attempted to exclude the `JF_AVOID_PREVIOUS_PR_COMMENTS_DELETION` altogether and send the...

@vinodhini-devops, If the env var was not set, I would expect to see at the `DEBUG` log: ``` Looking for an existing Frogbot pull request comment. Deleting it if it...