9 September: Merge rules, improved language selection and more
New ways to control when change requests are merged and by whom, plus improvements to localization support, change requests and more
Last updated
Was this helpful?
New ways to control when change requests are merged and by whom, plus improvements to localization support, change requests and more
Last updated
Was this helpful?
Was this helpful?
With this release, we’ve introduced merge rules for change requests.
Merge rules let you define specific requirements that must be met before a change request can be merged. You can set rules within each individual space, or set rules that apply across your entire organization, which you can then override within a single space if needed.
We’ve made it easy to configure with a bunch of presets to match your team’s requirements — from requiring the change request to have a subject, to requiring review from specific members. You can combine rules in any way you like to build more complex workflows, as well as write dynamic expressions using the same language as for adaptive content.
When a change request hasn’t met all the merge requirements, the Merge button is disabled and a tooltip explains why it can’t be merged.
We’re rolling this out starting with early access users today. It will be available for everyone on the Pro plan soon. This feature has been requested a lot recently, so we’re super happy to ship it!
If you’ve used translations to localize your site into different languages, we’ve improved your users’ experience when browsing your docs.
A new language picker now appears in the top-right of the screen, allowing site visitors to select their preferred language — and that language will be maintained when navigating between site spaces and within search results.
We’ve also added language options to the Structure section of your docs site settings, allowing you to quickly and easily select the UI language for your docs site as well.
Change requests just got more powerful, with a new sidebar that lets you add a description and easily view and add reviewers.
Open the Overview sidebar in a change request and you can see its status, quickly copy a link to it, add a description and manage reviewers. The UX should be familiar to anyone who uses GitHub.
This will become especially useful with the upcoming launch of Docs Agents, but it also allows you and your team to add more context to change requests and more easily manage your review flow — especially when paired with merge rules.
You can now vertically align content in a column block. It’s ideal for creating centered or bottom-aligned content — such as when building landing pages or adding context to an image.
You can now choose more display options when it comes to card images.
Previously, images would automatically be cropped to either 16:9 or 1:1 depending on your readers’ screen size. But that meant your images could sometimes be cropped incorrectly, and portrait images would never display in full.
Now, you can choose between three options:
The image crops to 16:9 or 1:1 as before.
The image stretches to fill the entire box.
The image displays in full within the constraints of the box, with your primary color filling any background space.
We’re constantly working to improve the way you and your team work in GitBook and value your input on features, bugs, and more. Make sure you head to our official GitBook community to join the discussion.