> ## Documentation Index
> Fetch the complete documentation index at: https://semgrep-ee9d73d8-abhijna-tec-647-weekly-release-notes.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.
# Enable Bitbucket Data Center pull request comments
**YOUR DEPLOYMENT JOURNEY**
* You have gained the necessary [resource access and permissions](/deployment/checklist) required for deployment.
* You have [created a Semgrep account and organization](/deployment/create-account-and-orgs).
* You have [connected your source code manager](/deployment/connect-scm).
* Optionally, you have [set up SSO](/deployment/sso).
* You have successfully added a [Semgrep job](/deployment/add-semgrep-to-ci) to your CI workflow with [diff-aware scanning](/deployment/customize-ci-jobs/#set-up-diff-aware-scans).
Semgrep can create **pull request (PR) comments** in your Bitbucket repository. These comments provide a description of the issue detected by Semgrep and may offer possible solutions. They are a means for security teams, or any team responsible for creating standards to help their fellow developers write safe and standards-compliant code.
## Conditions for PR comment creation
PR comments appear for the following types of scans under these conditions:
| Type of scan | Product name | Trigger condition | How to set up |
| :----------------------------------------- | :------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Static application security testing (SAST) | Semgrep Code | A comment appears when Semgrep generates a finding for a rule included in a [remediation policy](/semgrep-appsec-platform/unified-policies/overview) configured to leave PR or MR comments. This lets you customize which findings generate comments for developers. | Complete the steps in the following sections:
1. [Confirm your Semgrep account's connection and access to your source code manager](#confirm-your-semgrep-accounts-connection).
2. [Configure pull request comments](#configure-pr-comments). |
| Software composition analysis (SCA) | Semgrep Supply Chain (SSC) | A comment appears based on the conditions you explicitly set in a [remediation policy](/semgrep-appsec-platform/unified-policies/overview) or when Semgrep detects a [license violation](/semgrep-supply-chain/license-compliance). | To receive Supply Chain comments, complete the steps in [Confirm account connection and access](#confirm-your-semgrep-accounts-connection) and [set up a policy](/semgrep-supply-chain/policies).
To receive license violation comments, [enable dependency search](/semgrep-supply-chain/dependency-search#enable-and-use-dependency-search). |
| Secrets | Semgrep Secrets | A comment appears when Semgrep generates a finding for a rule included in a [remediation policy](/semgrep-appsec-platform/unified-policies/overview) configured to leave PR comments. | Complete the steps in the following sections:
1. [Confirm your Semgrep account's connection and access to your source code manager](#confirm-your-semgrep-accounts-connection).
2. [Configure pull request comments](#configure-pr-comments). |
## Enable PR comments in Bitbucket
### Prerequisites
* You must have a Bitbucket Data Center HTTP access token. Ensure that the [HTTP access token that you create](https://confluence.atlassian.com/bitbucketserver/http-access-tokens-939515499.html) has been granted **Project write** permissions. You'll provide this token to your CI provider during the setup process.
* Semgrep has been tested with Bitbucket Data Center v8.19. If you are using a different version of BBDC and there are issues, please [reach out to support](/support).
### Confirm your Semgrep account's connection
Confirm that you have the correct connection and access:
In your Semgrep AppSec Platform account, click **Settings > Source code managers**.
Check that an entry for your Bitbucket project exists and is correct.
#### Triage through PR comments
Developers can triage Semgrep findings without leaving Bitbucket by responding to the PR comments authored by Semgrep. Semgrep requires Bitbucket Data Center source code manager (SCM) connections to use an HTTP access token with **Project admin** permissions, so your connection may already use an appropriate token.
If you do not, to update your connection between Semgrep and Bitbucket Data Center:
Ensure that you're using Bitbucket Data Center version 8.8 or later.
Log in to Bitbucket using an account assigned with the **Project Admin** role.
See [Bitbucket Data Center HTTP access token requirements](/deployment/managed-scanning/bitbucket#bitbucket-data-center) to create or update your token.
Return to Semgrep and [ sign in](https://semgrep.dev/login).
Go to ** Settings > Source code managers**, and find your Bitbucket connection.
Click **Update access token**.
In the **Update access token** dialog that appears, provide the new token you created. Click **Update** to save and proceed.
Toggle the **Incoming webhooks** setting on.
Once you've successfully enabled webhooks and the **Default developer triage permissions** toggle is on, developers can triage Semgrep findings from Bitbucket Data Center.
## Configure PR comments
Once you have set up the connection between Semgrep and Bitbucket, you can [create a remediation policy](/semgrep-appsec-platform/unified-policies/get-started#create-a-remediation-policy) that lets you define the conditions under which Semgrep leaves a pull request comment. This customization enables you to:
* Manage the amount of PR comments your developers receive.
* Ensure that only rules that meet your criteria, such as high severity or high confidence rules, produce comments visible to developers, reducing noise.
## Optional features
### Customize PR comments
You can customize the comments Semgrep leaves on your PR. Custom comments allow you to direct your teams to the resources they need to handle the vulnerabilities Semgrep identifies in their code.
To provide custom PR comments:
Sign in to [ Semgrep AppSec Platform](https://semgrep.dev/login?).
Navigate to **Settings > General > Global**.
Go to the **Custom PR/MR comments footers** section.
Provide a custom comment for each Semgrep product whose findings you want to generate a PR comment. Semgrep supports Markdown and plaintext links in your message.
Click **Save changes**.
### Enable Rule-defined fix in Bitbucket Data Center repositories
[Autofix](/writing-rules/rule-defined-fix) is a Semgrep feature in which rules contain suggested fixes to resolve findings.
To enable **Rule-defined fix** for all projects in your Semgrep AppSec Platform organization, follow these steps:
In Semgrep AppSec Platform, go to **Settings > General > Code**.
Use the **Rule-defined fix ** toggle to enable this feature.
## Next steps
You've finished setting up a core deployment of Semgrep 🎉.
* Explore recommended tasks after deployment in [ Beyond core deployment](/deployment/beyond-core-deployment).
## Additional references