This help article guides you through the steps to view Cubyts Nebula AI -discovered issues in a PR/MR and use them to decide whether to merge it into the desired master branch.
Step 1: Steps to install/configure the Merge check application in Gitlab/Github/Bitbucket:
- Refer to this article to install/configure the merge check application for Gitlab.
- Refer to this article to install/configure the merge check application for GitHub (Free and Teams subscription).
- Refer to this article to install/configure the merge check application for GitHub (Enterprise subscription).
- Refer to this link to install/configure the merge check application for Bitbucket.
Step 2: Steps to grant access to relevant repositories for the Merge Check application in GitLab, GitHub, and Bitbucket:
- Refer to this article to configure repositories for Gitlab.
- Refer to this article to configure repositories for GitHub (Free, Teams, and Enterprise subscription).
- Note: No specific step in required for Bitbucket. The Bitbucket application has access to all the code repositories in the installation.
Stepf 3: Enabling flags in Cubyts for Merge check:
1. Finalize the list of technology flags that are critical for merge check. You can check out all the activated flags in your workspaces by navigating to the flags configurations page.
2. Enable the 'View flagged issues pre-merge' setting for important technology flags. This ensures that a PR carrying these issues is not merged into the target branch by the engineering lead.
3. In addition, specify the severity level to ensure that only the right severity levels are picked and shown in a PR (in Gitlab/Github/Bitbucket) .
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article