Version of the pipe: 3.2.0
Hello, I am using the above version of the git-secret-scan to create a pipeline to scan for any committed secrets in a pull request.
While I got the pipe to run and generate a report, I am having trouble getting the inline annotations to work. We have the pipe steps defined as a shared pipeline, like this:
export: true
Looking further into the pipe's code, it looks like the "path" and "line" properties in the query_annotation dictionary was removed.
https://bitbucket.org/atlassian/git-secrets-scan/pull-requests/35/diff
Perhaps this was intentional, but it may be the reason inline annotations are not working anymore. Or I misunderstood what inline annotation mean and that what they have currently (link in the report itself that will direct you to the line of code) is what the expected behavior is.
Hello and Welcome to Atlassian Community @Yuri Uchida
Maybe this older topic from 2025 will be helpful for you.
Solved: atlassian/git-secrets-scan does not annotate the c...
Best,
Arek🤠
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for the post. I did look at this, and my issue isn't that the links are pointing to the wrong commit, it just isn't showing up inline in the diff view in PRs, which is what I was expecting
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Okay, I will take a deeper look on this this weekend.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.