Codebeat analyses every pull request when you add a new private project using Github, Bitbucket or Gitlab.
Enabling pull request feature.
Every private project has a Pull Requests tab on it's dashboard. If you find it empty even though you have some open PR's, make sure to push a new commit to your repository so that codebeat can trigger a sync. While you can find an overview of all PRs on the list, the single PR page gives much more in-depth information.
The header includes basic quality information about a given PR. Apart from data like pull request name, commit hash and branch name, you will find three icons summarising introduced, fixed, and changed issues, grouped by their category: Complexity Issues, Namespace Level Issues and Duplications.
After scrolling down to the Report section you'll find a list of entries representing quality changes that have been introduced by your PR. Moreover, for every grade change you can see a full issue summary and code diff by clicking one of two buttons on the right. This way no introduced or degraded issue will pass through your code review unnoticed.
In some cases you might want to manually close a pull request on codebeat to remove it from the list (it might be old and neglected for instance). This can be achieved by clicking Close button on pull requests list.
This will only close the pull request in codebeat.
codebeat only analyses Pull Requests if the target branch is the one tracked by codebeat.
Updated almost 5 years ago