Skip to content

GitLab Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
www-gitlab-com
www-gitlab-com
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 2,171
    • Issues 2,171
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 1,238
    • Merge Requests 1,238
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • GitLab.com
  • www-gitlab-comwww-gitlab-com
  • Merge Requests
  • !42424

Merged
Opened Mar 02, 2020 by Carolyn Bednarz@cbednarzMaintainer2 of 2 tasks completed2/2 tasks

Update source/handbook/people-group/how-to-reach-us/index.html.md

  • Overview 0
  • Commits 1
  • Pipelines 2
  • Changes 1

Why is this change being made?

Lorna and I had made a slight tweak in the teams that we will be supporting. Updating the handbook to reflect the correct mapping.

Describe in detail answer to question on why this change is being proposed, in accordance with our value of Transparency

-->

Does this MR meet the acceptance criteria?

Assign to DRI

  • Did you assign this change to the correct DRI of the page or information you are changing?

Conformity

  • Added description to this MR explaining the reasons for the proposed change, per say-why-not-just-what
Edited Mar 02, 2020 by Trevor Knudsen
Assignee
Assign to
Reviewer
Request review from
None
Milestone
None
Assign milestone
Time tracking
Reference: gitlab-com/www-gitlab-com!42424
Source branch: cb-update-pbp-alignment

Revert this merge request

This will create a new commit in order to revert the existing changes.

Switch branch
Cancel
A new branch will be created in your fork and a new merge request will be started.

Cherry-pick this merge request

Switch branch
Cancel
A new branch will be created in your fork and a new merge request will be started.