Skip to content
This documentation applies to Codacy Self-hosted v4.1.0

For the latest updates and improvements, see the latest Cloud documentation instead.

How do I reanalyze my repository?#

To reflect the most recent configurations for your repository on the Codacy analysis results without waiting for a new commit to trigger the analysis, reanalyze the last commit in your branch or pull request.

Important

If you have the setting Run analysis through build server enabled in your repository Settings page so that you can run client-side tools you can't trigger a new analysis from the Codacy UI.

Instead, you must manually run the client-side tools or wait for them to report the results for a new commit.

Reanalyzing a branch#

To reanalyze a branch in your repository:

  1. Open the Commits page for your repository and select the correct branch at the top of the page if you configured Codacy to analyze multiple branches.

    Then, select the most recent commit for that branch at the top of the list:

    Selecting the last commit on a branch

  2. Click the icon next to the Current status of the commit to trigger a reanalysis. Codacy will display a message when the analysis is complete.

    Reanalyzing a commit

Reanalyzing a pull request#

To reanalyze a pull request in your repository:

  1. Open the Pull Requests page for your repository and select the pull request that you want to reanalyze.

  2. Click the icon next to the Current status of the pull request to trigger a reanalysis. Codacy will display a message when the analysis is complete.

    Reanalyzing a pull request

Share your feedback 📢

Did this page help you?

Thanks for the feedback! Is there anything else you'd like to tell us about this page?

We're sorry to hear that. Please let us know what we can improve:

Alternatively, you can create a more detailed issue on our GitHub repository.

Thanks for helping improve the Codacy documentation.

If you have a question or need help please contact support@codacy.com.

Last modified April 29, 2021