Per Repository Settings Available With RhodeCode Enterprise 3.7.0

Published on November 09, 2015, by Brian


Per-repository settings are finally here! With this release of RhodeCode Enterprise we are very pleased to announce that with this new feature you can now configure single repositories to use a separate issue tracker, or set different default behaviour than what is configured globally across the instance.

This is another step in increasing the flexibility of RhodeCode Enterprise. This addition enables large organisations to integrate with as many issue trackers as are used across their myriad teams. From a developer's perspective, you can now set your preferred default behaviour for your own repositories or forks. Continue reading for more information, or check out the full release notes if you prefer.

Pull Requests

The pull request functionality was also the recipient of a new addition this release with the inclusion of an automated update review. This lists the added, updated, and removed files as a comment each time a pull request is updated. Meaning you don't have to recheck each file after an update and helps keep reviewers focussed on what is important when reviewing very large pull requests.

As part up the improvements around large pull requests, the main comments on a pull request are now submitted using ajax, so a page refresh is no longer required after you leave your feedback.

One additional clean up fix means the Add comment functionality is no longer displayed on closed pull requests, removing the temptation to have the last word on all discussions.

Pull Request Update

Interface and UX

The RhodeCode Enterprise interface has also been improved, and with support for IE8 sunsetting, the tweaks around alert messages and the changelog display will be the final solution for our support of that browser.

Our previously much misunderstood machine gun commenting feature has also been disabled. Heretofore if you rapidly clicked the Add Comment or Delete buttons you would end up with either duplicated content or a cryptic error message. UX feedback suggested that this feature was confusing for users unfamiliar with such arbitrary behavior so we have modified it to be more consistent with expectations.

A number of styling changes around the merge and preview buttons, and fixing the alignment of some UI components tops off this set of UI/UX changes.

Deprecation

Internet Explorer 8 support. This is the last release which officially supports IE8, so if you are using it with RhodeCode Enterprise, good luck with that!

Download & Upgrade Information

To download or upgrade RhodeCode Control and RhodeCode Enterprise, get the latest versions from our download portal and see the installation or upgrade documentation.