Skip to content

Conversation

@eyalk007
Copy link
Contributor

@eyalk007 eyalk007 commented Nov 3, 2025

  • All tests passed. If this feature is not already covered by the tests, I added new tests.
  • This pull request is on the dev branch.
  • I used gofmt for formatting the code before submitting the pull request.
  • Update documentation about new features / new supported technologies

@eyalk007 eyalk007 self-assigned this Nov 3, 2025
@eyalk007 eyalk007 added the ignore for release Automatically generated release notes label Nov 3, 2025
@eyalk007 eyalk007 added the safe to test Approve running integration tests on a pull request label Nov 3, 2025
@github-actions github-actions bot removed the safe to test Approve running integration tests on a pull request label Nov 3, 2025
@eyalk007 eyalk007 added the safe to test Approve running integration tests on a pull request label Nov 4, 2025
@github-actions github-actions bot removed the safe to test Approve running integration tests on a pull request label Nov 4, 2025
@eyalk007 eyalk007 closed this Nov 4, 2025
@eyalk007 eyalk007 reopened this Nov 4, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Nov 4, 2025

👍 Frogbot scanned this pull request and did not find any new security issues.


- Fix PullRequestSecretComments field access in comment.go
  (field is in Params.Git struct, not directly on Repository)
- Update GitLab validation to check notes and discussions separately
  GitLab uses separate APIs for regular comments (notes) and review
  comments (discussions), unlike other VCS platforms
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ignore for release Automatically generated release notes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants