Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SLVSCODE-966 publish taints notification #429

Conversation

sophio-japharidze-sonarsource
Copy link
Contributor

@sophio-japharidze-sonarsource sophio-japharidze-sonarsource commented Dec 27, 2024

@sophio-japharidze-sonarsource sophio-japharidze-sonarsource force-pushed the SLVSCODE-966_publishTaints_notification branch from 3da0c47 to 63f9c83 Compare December 27, 2024 14:16
@sophio-japharidze-sonarsource sophio-japharidze-sonarsource changed the base branch from master to SLLS-292_use_latest_analyzers December 27, 2024 14:17
Base automatically changed from SLLS-292_use_latest_analyzers to master January 2, 2025 10:41
@sophio-japharidze-sonarsource sophio-japharidze-sonarsource force-pushed the SLVSCODE-966_publishTaints_notification branch from 63f9c83 to 25b2cb2 Compare January 2, 2025 10:43
@sophio-japharidze-sonarsource sophio-japharidze-sonarsource marked this pull request as ready for review January 2, 2025 11:20
Copy link
Member

@jblievremont jblievremont left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍🏻 good catch!

@sophio-japharidze-sonarsource sophio-japharidze-sonarsource merged commit c4ca2fb into master Jan 6, 2025
7 checks passed
@sophio-japharidze-sonarsource sophio-japharidze-sonarsource deleted the SLVSCODE-966_publishTaints_notification branch January 6, 2025 10:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants