Comment only violations that relate to a diff about violation-comments-to-stash-plugin HOT 6 CLOSED

Yes that would be better. I did not manage to figure out how to determine if a reported line is changed in the pull request, or not.

The GitHub API was easier. There I made it optional to comment all changed files, or comment only changed parts of files: https://github.com/tomasbjerre/violation-comments-to-github-lib/blob/master/src/main/java/se/bjurr/violations/comments/github/lib/GitHubCommentsProvider.java#L112

from violation-comments-to-stash-plugin.

You may say that you encourage the boy scout rule =) So developers should clean up any file they touch.

from violation-comments-to-stash-plugin.

You may say that you encourage the boy scout rule =)

Ha 😄! I guess it's feasible and circumvents the problem.

I'm not really familiar with Atlassian APIs, but doesn't /rest/api/1.0/projects/{projectKey}/repos/{repositorySlug}/pull-requests/{pullRequestId}/diff at Bitbucket server REST API (anchors don't appear to work on that page so no direct link) seem to drive the need?

Documentation is a bit misleading, as you would first think that srcPatch is required parameter, but it actually isn't.

from violation-comments-to-stash-plugin.

I think it works now in 1.34 but I did not have time to test it alot.

Lines can be reported as ADDED, REMOVED or CONTEXT. I decided to include ADDED and CONTEXT. Because a change on line 10 may trigger a violation on line 9...

And to check if a line is in CONTEXT, the rest call is something like http://localhost:7990/rest/api/1.0/projects/TOM/repos/violations-test/pull-requests/1/diff.

from violation-comments-to-stash-plugin.

Actually I changed it again. 1.35 only includes ADDED. And there is a field, context, for specifying how many lines surrounding an added line that should be included.

from violation-comments-to-stash-plugin.

Sounds feasible, I'll give it a try. Thanks again!

from violation-comments-to-stash-plugin.