Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

#934: Use static report key for non-monorepo Bitbucket decoration #951

Merged
merged 1 commit into from
Sep 6, 2024
Merged

#934: Use static report key for non-monorepo Bitbucket decoration #951

merged 1 commit into from
Sep 6, 2024

Commits on Aug 18, 2024

  1. #934: Use static report key for non-monorepo Bitbucket decoration 

    The Bitbucket decoration is currently using the project key to create
the analysis report key, but the Sonarqube documentation states this
should be a static value across all projects. To ensure that the
Bitbucket `Required report` configuration can be created as per the
guidance in Sonarqube documentation, the static key is being used where
the repository has not been set as a monorepo.
    @mc1arke
    mc1arke committed Aug 18, 2024
    Configuration menu
    Copy the full SHA
    629f22a View commit details
    Browse the repository at this point in the history