Skip to content

Commit 556b11f

Browse files
authored
Update scan-bitbucket-server-pull-request.md
1 parent 88121d0 commit 556b11f

File tree

1 file changed

+5
-8
lines changed

1 file changed

+5
-8
lines changed
Lines changed: 5 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,8 @@
11
# Scan Bitbucket Server Pull Request
22

3-
After you create a new pull request, Frogbot will automatically scan it.
3+
**The JFrog Security documentation has a new home!**\
4+
You can now find it [here](https://jfrog.com/help/p/security-home), including sections on:
45

5-
_**NOTE:**_ The scan output will include only new vulnerabilities added by the pull request. Vulnerabilities that aren't new, and existed in the code before the pull request was created, will not be included in the report. In order to include all the vulnerabilities in the report, including older ones that weren't added by this PR, use the includeAllVulnerabilities parameter in the frogbot-config.yml file.
6-
7-
The Frogbot scan on Bitbucket Server workflow:
8-
9-
1. The developer opens a pull request.
10-
2. Frogbot scans the pull request and adds a comment with the scan results.
11-
3. Frogbot can be triggered again following new commits, by adding a comment with the `rescan` text.
6+
* [CLI](https://jfrog.com/help/r/jfrog-security-user-guide/developers/cli)
7+
* [Frogbot](https://jfrog.com/help/r/jfrog-security-user-guide/developers/frogbot)
8+
* [IDEs](https://jfrog.com/help/r/jfrog-security-user-guide/developers/ides)

0 commit comments

Comments
 (0)