Gitlab hero border pattern left svg Gitlab hero border pattern right svg

Servicing Internal Requests

On this page


For GitLab team members wanting to file an internal request, please see the Support Internal Requests handbook page.

This document details the various templates and workflows that should be followed in order to properly service GitLab.com related requests that Support receives in the internal-requests issue tracker.

Note: For internal requests relating to licenses and subscriptions, please refer to the relevant license and subscription workflow, or CustomersDot console workflow.

General Workflow

graph TD; A[Issue Created]-->B[Assign Yourself]; B-->C[Issue Actionable?]; C-->J[No]; J-->K[Apply Status::Blocked and Inform Submitter]; C-->D[Yes]; D-->E[Take Action]; E-->F[Issue Resolved?]; F-->G[Yes]; G-->H[Close, or Apply Status::Awaiting Confirmation and inform submitter]; F-->I[No]; I-->L[Requires waiting?]; L-->M[Yes]; M-->N[Apply Status::On-Hold and set due date]; L-->O[No]; O-->P[Escalate as necessary];

Inactive Namespace Request

See Name Squatting Policy.

Contact Request

GitLab team members, primarily infra, will use this template to request Support to contact a user on their behalf. If requested to do this via Slack, open an issue on behalf of the requester.

The requestor should contact the CMOC to fulfill the request.

This typically requires GitLab.com admin access, because you will need to look up the relevant email addresses.

See the Sending notices workflow for more details. If none of the listed cases apply, you can use the GitLab.com::Notices::General Contact Request macro. Leave an internal note with a link to the issue.

Repo Size Limit Increases

Should a user request a temporary extension of the size limit of their repository the following workflow should be used if that extension is granted.

  1. Open an issue in the internal-requests issue tracker using the Repo Size Limit issue template.
  2. Apply the Status::On Hold label and set the due date to when it should be reverted.
  3. Using your GitLab.com admin account navigate to the project in question while appending /edit to the URL. For example, if the project in question is located at https://gitlab.com/group/subgroup/project/ you would navigate to https://gitlab.com/group/subgroup/project/edit.
  4. Enter a new value in the Repository size limit (MB) field.
  5. Click Save changes.
  6. Revert the size limit back to the default on the specified due date.

Pipeline Quota Reset

See internal wiki page.

GitLab.com Console Escalation

This is a generic template used to request an engineer with GitLab.com console access to take action.

Common issues include the following when the UI and API methods are not working:

Engineers with console access should search for similar previous requests, look for the relevant function in the code, or work with another engineer to resolve each request.

Any request requiring disk access requires an infra issue.

Soft-Deleted Project

See the Project deletion workflow for information on when this template is used.

Engineers with GitLab.com console access will attempt to delete the project.

Git is a trademark of Software Freedom Conservancy and our use of 'GitLab' is under license