2019-08-22 Newly created unlabelled issues requiring initial triage

Hi Triage Team,

Here is a list of the latest issues without labels in the project.

In accordance with the Partial triage guidelines, we would like to ask you to:

1. Check for duplicates in this project and others (it is common for issues reported in EE to already exist in CE).
2. Add a type label.

• If identified as a bug, add a severity label.
• If the severity is ~S1 or ~S2, mention relevant PM/EMs from the relevant stage group from product devstages categories.

1. Add a team label.
2. Add a stage label.
3. Add relevant subject labels to facilitate automatic addition of stage and group labels.
4. If needed, mention relevant domain experts if the issue requires further attention.

For the issues triaged please check off the box in front of the given issue.

Once you've triaged all the issues assigned to you, you can unassign yourself with the /unassign me quick action.

When all the checkboxes are done, close the issue, and celebrate! 🎉

@jennielouie

• #13708 (closed) Mirroring from private gitlab to gitlab.com using deploy tokens succeeds initially but fails with bogus error later

@tpazitny

• #13702 (closed) Two pipelines created when committed with [skip -ci]

@wlsf82

• #13701 (closed) API endpoints for adding and removing specific labels

@mlapierre

• #13700 (moved) Configure Admin users as Grafana Admins

@at.ramya

• #13683 (closed) whether i can use "include" only for .gitlab-ci.yml ?

@ddavison

• #13670 (closed) Unable to clone when gitlab is migrated to HTTPS

@asoborov

• #13667 [Container Scanning] Add information about image name