Bitbucket Comment Reporter
May 5, 2026 ยท View on GitHub
Posts MegaLinter results summary in the comments of the related Bitbucket pull request (if existing)
Usage
Click on hyperlinks to access detailed logs (click on Download in Artifacts section at the left of a CI job page)
If LLM Advisor is activated, it will also show its suggestions to fix linter errors.
After a first MegaLinter run, a comment is posted on the PR. To avoid multiplicating MegaLinter PR comments, future MegaLinter runs will update the existing PR comment instead of posting a new one.
If you really want a new PR comment for each MegaLinter run, define variable BITBUCKET_COMMENT_REPORTER_OVERWRITE_COMMENT to false.
Configuration
- Create a Repository Access Token with scope Pull-requests: Write
- Paste the access token in a masked CI/CD variable named BITBUCKET_REPO_ACCESS_TOKEN in your project (repository)
| Variable | Description | Default value |
|---|---|---|
| BITBUCKET_COMMENT_REPORTER | Activates/deactivates reporter | true |
| BITBUCKET_REPO_ACCESS_TOKEN | Must contain a Bitbucket repository access token defined with api access | |
| BITBUCKET_COMMENT_REPORTER_OVERWRITE_COMMENT | Set to false to not overwrite existing comments in case of new runs on the same Pull Request | true |
| REPORTERS_MARKDOWN_TYPE | Set to simple to avoid external images in generated markdown | advanced |
| REPORTERS_MARKDOWN_SUMMARY_TYPE | Display summary in PR/MR comments as sections, table or both (sections-table or table-sections) | table-sections |
| REPORTERS_ACTION_RUN_URL | Override default URL of the CI job visualization page | |
| JOB_SUMMARY_ADDITIONAL_MARKDOWN | Custom markdown to add at the end of the summary message | |
| MEGALINTER_MULTIRUN_KEY | Key to identify multirun when multiple MegaLinter runs are executed in the same pipeline (ex: java) |
Jenkins Support
This reporter also works when MegaLinter is triggered from a Jenkins Multibranch Pipeline. See Jenkins installation guide for details.