The Commits page displays an overview of the commits in your repository, such as the analysis status and the number of new and fixed issues for each commit. This allows you to monitor the evolution of the code quality in your repository per commit.
By default, the page lists the commits on the main branch of your repository but if you have more than one branch enabled you can use the drop-down list at the top of the page to display issues on other branches.
Click a specific commit to see detailed information about the code quality changes introduced by that commit.
The next sections describe each area of the commit detail page.
This area displays the information that identifies the commit (SHA hash, date, and commit message), as well as:
- The analysis status and a button to reanalyze the commit
- A link to the analysis logs
- A link to the commit on your Git provider
Commit quality overview#
This area displays the quality gate status and an overview of the code quality metrics for the commit:
The quality gate status is either Not up to standards or Up to standards depending on the quality gate rules for your repository.
If you don't have any rules enabled for commits, the status is always Up to standards.
The changes to the following code quality metrics introduced by the commit are displayed either as a positive or negative variation, or no variation (represented by
- Issues: Number of new or fixed issues
- Duplication: Number of new or fixed duplicated code blocks
Complexity: Variation of complexity
Coverage: Variation of code coverage percentage relative to the parent commit
Depending on the languages being analyzed or if you haven't set up coverage for your repository, some metrics may not be calculated (represented by
The colors depend on the quality gate rules for your repository:
- Green: The metric passes the quality gate
- Red: The metric fails the quality gate
- Gray: There aren't quality gate rules configured for the metric
If you change the quality gate rules you must reanalyze the commit to update the color of the metrics, except for coverage which updates immediately after you save your changes on the Quality Settings page.
The New Issues and Fixed Issues tabs display the list of issues that the commit created or fixed.
Click the title of an issue to see the following information:
- The contributor and date of the commit that introduced the issue
- The tool that reported the issue and the estimated time to fix it
- What's the issue and how to solve it
- The programming language and category of the issue
Use the options in the cogwheel menu of each issue to ignore and manage issues.
In some situations, Codacy may report either new or fixed possible issues on a commit, which means that the code analysis detected these issues in lines of code that weren't changed by that commit. This gives you awareness to how your changes may be affecting other parts of your code.
The following are example situations that can lead to possible issues:
The issue was either created or fixed in the current commit, but the static code analysis tools reported the issue on a line that didn't change in the commit. For example, if you remove the line containing the declaration of a variable you may get an "undeclared variable" issue in other lines that use that variable.
If a file had more than 50 issues reported by the same tool and you push a new commit that fixes some of these issues, Codacy will report more issues until the limit of 50 issues. These issues will be possible issues if they're outside the lines of code changed in the new commit.
If you're using GitHub you may see annotations for possible issues reported under Unchanged files with check annotations on the Files changed tab of your pull requests.
This happens when Codacy reports possible issues in files that weren't changed in your pull request. Read more about this GitHub feature.
The New Duplication and Fixed Duplication tabs display the list of duplicated blocks that the commit created or fixed.
The Files tab displays an overview of the code quality changes introduced by each file that was either changed in the commit or that had code coverage data reported.
The Diff tab displays the line differences in each file that was changed in the commit.
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?
255 characters left
We're sorry to hear that. Please let us know what we can improve:
255 characters left
Alternatively, you can create a more detailed issue on our GitHub repository.
Thanks for helping improve the Codacy documentation.
Edit this page on GitHub if you notice something wrong or missing.
If you have a question or need help please contact firstname.lastname@example.org.