Merge requests requiring attention

Hi merge request coaches (@gitlab-org/coaches),

Here is a list of merge requests that were opened recently.

These Merge Requests were chosen, as they meet the following criteria:

  • Open
  • No labels
  • Author not in the gitlab-org group

We'd like to ask you to determine whether:

  • The MR is ready or further changes are required
  • The MR should be assigned to a reviewere
  • The MR should be closed down

Here is a list of merge requests that are inactive for some time.

These Merge Requests were chosen, as they meet the following criteria:

  • Open
  • Labelled Community contribution and not labelled coach will finish
  • No activity in the past 2 months

We'd like to ask you to determine whether:

  • The MR is ready or further changes are required
  • The MR should be taken over by the team
  • The MR should be closed down
  • WIP: Add /relate command 1st contribution, Community contribution, ~"Plan", issues, quick actions
  • As the text is free, Why is the omniauth button width constrained ? 1st contribution, Community contribution, UX
  • support sync name from ldap close #1974 1st contribution, Community contribution, ldap
  • i18n: externalize strings from 'app/views/projects/pipelines' Community contribution, auto updated, awaiting feedback
  • i18n: externalize strings from 'app/views/projects/issues' Community contribution, auto updated, awaiting feedback

For the Merge Requests triaged please check off the box in front of the given MR.

Thanks for your help!

Edited Mar 15, 2019 by Dennis Tang
Assignee Loading
Time tracking Loading