Add latest changes from gitlab-org/gitlab@master

app/assets/javascripts/issuable_context.js

 import $ from 'jquery';
 import Cookies from 'js-cookie';
-import bp from './breakpoints';
+import { GlBreakpointInstance as bp } from '@gitlab/ui/dist/utils';
 import UsersSelect from './users_select';
 export default class IssuableContext {
@@ -48,7 +48,9 @@ export default class IssuableContext {
     window.addEventListener('beforeunload', () => {
       // collapsed_gutter cookie hides the sidebar
       const bpBreakpoint = bp.getBreakpointSize();
-      if (bpBreakpoint === 'xs' || bpBreakpoint === 'sm') {
+      const supportedSizes = ['xs', 'sm', 'md'];
+
+      if (supportedSizes.includes(bpBreakpoint)) {
         Cookies.set('collapsed_gutter', true);
       }
     });

doc/user/admin_area/settings/visibility_and_access_controls.md

@@ -16,7 +16,6 @@ To access the visibility and access control options:
 This global option defines the branch protection that applies to every repository's default branch. [Branch protection](../../project/protected_branches.md) specifies which roles can push to branches and which roles can delete
 branches.  In this case _Default_ refers to a repository's default branch, which in most cases is _master_.
-branches.  "Default" in this case refers to a repository's default branch, which in most cases would be "master".
 This setting applies only to each repositories' default branch. To protect other branches, you must configure branch protection in repository. For details, see [Protected Branches](../../project/protected_branches.md).