A Chrome extension to warn a user if a pull request that can be merged contains multiple commits.
Bitbucket Merge Check Extension
If a pull request has multiple commits, it can be configured to:
- change the colour of the web page around the 'Merge' button to 'Yellow' to visibly warn the user that the pull request contains multiple commits
- when the 'Merge' button is clicked, prompt the individual to confirm that the merge operation should proceed with multiple commits being merged
- display the number of commits in the pull request in the text of the 'Merge' button
If a pull request has only a single commit, it can be configured to change the colour of the web page around the 'Merge' button to 'Green' to indicate that it is safe to merge the pull request.
If a pull request cannot be merged, it can be configured to change the colour of the section around the 'Merge' button to 'Grey' to indicate that the pull request cannot be merged.
Commit Message Widening:
The extension can be configured to allow for widening of commit message pop-up dialogs so they will wrap at around 80 characters in length. If commit messages follow best practices of stopping around 72-75 characters, this means no wrapping will occur. As a result, the commit messages look better (no unexpected short lines, due to early wrapping of the prior line) are easier to read because they will wrap when the author intended.
This feature can be enabled/disabled by the 'Widen Commit Message Popup' option in the configuration options of the extension.
Pull Request List Highlighting:
The extension can be configured to highlight pull requests in the list of pull requests with a background colour so that the status of the pull request is more immediately evident to a reviewer.
Pull requests are highlighted with the following background colours:
* red: A build has failed
* yellow: There are conflicts or a reviewer has marked the pull request 'Needs Work'
* blue: A build is in progress or has succeeded; it needs review (no reviewer has marked the pull request 'Needs Work' or 'Approved')
* green: A build has succeeded and a reviewer has marked the pull request 'Approved'
This feature can be enabled by the 'Highlight Pull Requests' option in the configuration options of the extension.
Add Jira Status to Branch List Information:
The extension can be configured to add the status of the Jira issue into the information displayed for the list of branches.
By default, for each branch in the repository, Bitbucket provides the Jira issue associated with the most recent commit. This feature queries Jira to determine the status of the issue and includes this information in what is displayed, so it is easier to make a decision about a branch at a glance.
This feature can be enabled by the 'Add Jira Status to Branches List' option in the configuration options of the extension. A Jira host and token must be configured in the extension options in order to enable this feature.
Order Tags in Drop-down Lists:
The extension can be configured to order the tags displayed in the 'Tags' dropdown list according to Semantic Versioning v2 with the most recent version displayed at the top of the list.
By default, Bitbucket provides the tags in the order in which they were created which can make it difficult to locate an older tag by scrolling the list as the tag may appear randomly in the list (applying a filter is really the only solution to reliably locate it).
This feature can be enabled by the 'Order Tags in Drop-down Lists' option in the configuration options of the extension.
Pull Request Jira Issue Version Information
The extension can be configured to display the version information for the Jira issue that is associated with a pull request. When enabled, if an associated Jira issue's `fixVersions` field is populated with values, the versions will be displayed immediately below the link to the Jira issue.
Additionally, the link to the Jira issue is given a tooltip of the Jira issue's summary so that this information is more easily accessible to the reviewer.
This feature can be enabled by the 'Order Tags in Drop-down Lists' option in the configuration options of the extension.
Notes:
This extension is only applicable to Bitbucket Server 7 and beyond; it does not work with Bitbucket Cloud or Bitbucket Server 6 and lower.
Change Log:
2.7 (2024-12-11)
* Remove the unused `activeTab` permission from the manifest
2.6 (2024-12-02)
* Update npm package dependencies
* Improve the instructions for host name values
* Gracefully handle a failure to retrieve Jira information
* Address 'merge check' issues introduced by the the recently added 'auto-merge' feature.
* Add the display of version information for Jira issues associated with pull requests.
2.5 (2023-02-13)
* Update to Chrome Extension Manifest format v3.
* Order tags according to Semantic Versioning v2 with the latest version appearing at the top of the list.
2.4 (2022-09-07)
* Add the status of the Jira issue next to the Jira issue id in the Bitbucket branches list of a repository.
2.3 (2022-08-08)
* Correct an issue where the width of commit message pop-ups on pull request
pages were not extended.
* Correct an issue where feature-specific styles were enabled/active when the
associated feature was disabled in extension options.
- Feature-specific styles are only enabled now when the feature is enabled.
2.2 (2022-08-02)
* Highlight pull requests when viewing them in the pull requests list so that
the status is more clearly communicated to reviewers.
- The rows are highlighted as follows (worst -> best):
* red: A build has failed
* yellow: There are conflicts or a reviewer has marked the pull request
'Needs Work'
* blue: A build is in progress or has succeeded; it needs review (no
reviewer has marked the pull request 'Needs Work' or 'Approved')
* green: A build has succeeded and a reviewer has marked the pull request
'Approved'
2.1 (2021-04-05)
* Extend the width of the Bitbucket commit message pop-up
- When hovering over a commit or a message in a pull request or commit
list, Bitbucket displayed a pop-up window with the Git commit message
that wrapped at approximately 60 characters with font-family 'monospace'
and font-size '12px'
- By extending the width, Git commit messages that adhere to the standard
width of 72 characters are not displayed with wrapped lines
2.0 (2021-03-01)
* Support for Bitbucket Server 7+
- Tested with Bitbucket Server 7.6 (LTS)
- Bitbucket Server 6 and lower are no longer supported.
1.0 (2020-04-01)
* Initial version
Source Manifest.json
How to download and manually install Bitbucket Merge Check extension for Chrome
Looking for a way to install Bitbucket Merge Check extensions for Chrome, you can search for them in the Chrome Web Store, clicking the "Add to Chrome" button, and following the straightforward process.
However, you may need to install Bitbucket Merge Check extensions manually, this article outlines two simple methods to effortlessly install Bitbucket Merge Check extensions, whether they come as unpacked folders in compressed formats like .zip or as .crx files.
Method 1: Download Bitbucket Merge Check extension and manually install through Drag &Drop
If you ever need to manually install a Bitbucket Merge Check extension for Chrome, don't worry, it's a simple process. Just follow these easy steps, and you will have your extension ready to use in no time.
Step 1: Download the Bitbucket Merge Check Extension by clicking the "Download CRX" button on the website.
Look for the Bitbucket Merge Check extension you wish to install. Go to the website and download the Bitbucket Merge Check extension package, which is usually a .CRX file and comes in a zipped file. Here ".crx" file is the format for Bitbucket Merge Check extension that contains all the data.
Step 2: Extract &Arrange Files
Once the file is downloaded, extract that file into its own folder. Similarly, give that extension files a permanent home. In other words, keep it in a folder that you don't accidentally delete it because these files will be needed to make that extension work.
Step 3: Go to the Chrome Extensions Page
Open Google Chrome and in the address bar, type chrome://extensions; it will open the Google Chrome extensions page. Make sure that "My extensions" is selected in the sidebar.
Step 4: Drag and Drop the Extension
Now, go to the folder where you extracted the Bitbucket Merge Check extension and drag &drop the extension file from there anywhere onto the extension page within Google Chrome.
Step 5: Complete the Installation
Once you drag and drop the extension file, follow the steps that Google Chrome takes you through. Similarly, if the extension file is of .crx file format, you will be required to review the permissions and then add the extension.
Now, you can manage that added extension as you would like to with any other Chrome extension that you added through Chrome Webstore. Its icon will also appear in the Google Chrome Menu on the right side of the address bar once you activate it.
Method 2: Download Bitbucket Merge Check extension for Chrome and install in Developer Mode
This is another method to install Bitbucket Merge Check extension manually, but the twist is that here, you install by enabling the developer mode option provided in Google Chrome. This mode is commonly used for testing extensions or running unpublished tools.
Step 1: Download the Bitbucket Merge Check extension file
Select and download the Bitbucket Merge Check extension by clicking the 'Download CRX' button on the website.
Step 2: Extract the downloaded contents
Convert the file to a ZIP file if it is in CRX format then extract the Bitbucket Merge Check extension zip file or folder that you downloaded. Make sure you extract it using the same folder name and keep it safely in another folder, so you don't delete it by mistake. The extracted folder will be needed to keep your Bitbucket Merge Check extension running.
Step 3: Open Chrome Extension Setting Page
In the address bar of Google Chrome, type chrome://extensions and open the Chrome Extension Page.
Step 4: Enable Developer Mode
After opening the Chrome Extension page, look at the top right side, and you will find the toggle option of "Developer mode."Simply enable that developer mode option.
Step 5: Load the Unpacked Extension
Once you enable the developer mode option, you will see the menu of Load Unpacked, Pack Extensions and Update. From that, select the option "Load unpacked."
Step 6: Select the Extension Folder
Once the pop-up opens upon clicking Load unpacked, select the Bitbucket Merge Check extension directory and click on the "Select Folder "button.
Step 7: Confirm and Install
After you select an extension folder of a Google Chrome extension you're installing manually, confirm its installation for the final time and let the installation complete.
Conclusion
Here we've made a step-by-step guide on How to manually install Bitbucket Merge Check extension in 2 ways. We hope this guide proves helpful.
Similar Extensions
Google Apps Script GitHub Assistant 19 98 ★ 153KiB
Screen Shader | Smart Screen Tinting 19 1439 ★ 140KiB
Who Am I 19 0 ★ 420KiB
React code finder 19 5 ★ 2.95MiB
Bulk URL Opener 19 46 ★ 242KiB
Obsidian Web 19 67 ★ 641KiB
Cast to Sonos 19 30 ★ 398KiB
Save as Shortcut 19 109 ★ 398KiB
Mokku 19 76 ★ 3.28MiB
Copy as Plain Text 19 24 ★ 39.63KiB
Chrome extension source viewer 19 422 ★ 227KiB
Death To _blank 19 79 ★ 196KiB
Bulk Image Downloader From Url List 19 46 ★ 1.38MiB
Perplexity AI 19 22 ★ 874KiB
Clutter Free - Prevent duplicate tabs 19 203 ★ 411KiB
Promptalot Helper 19 58 ★ 347KiB
Extension Manager 19 6 ★ 15.29KiB
YAML Validator 19 2 ★ 292KiB
UX Enhancer for GitLab 19 7 ★ 115KiB
Initab 19 95 ★ 12.93MiB
Multiple Url Opener 19 2 ★ 15.96KiB
마우스 제스처 크롬 확장 프로그램 19 28 ★ 117KiB
Zoho QEngine Recorder 19 3 ★ 741KiB
Tab Manager Plus for Chrome 19 1001 ★ 477KiB
User reviews
Mark Koopman (ID: 00000039af183e4e) Voted 5 ★ - Updated 11/18/2020