# How to create a merge request
> 原文:[https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
* [New Merge Request page](#new-merge-request-page)
* [Create Merge Request button](#create-merge-request-button)
* [New merge request by adding, editing, and uploading a file](#new-merge-request-by-adding-editing-and-uploading-a-file)
* [New merge request from a new branch created through the UI](#new-merge-request-from-a-new-branch-created-through-the-ui)
* [New merge request from your local environment](#new-merge-request-from-your-local-environment)
* [New merge request from an issue](#new-merge-request-from-an-issue)
* [New merge request from the Merge Requests page](#new-merge-request-from-the-merge-requests-page)
* [New merge request from a fork](#new-merge-request-from-a-fork)
* [New merge request by email](#new-merge-request-by-email-core-only)
* [Adding patches when creating a merge request via e-mail](#adding-patches-when-creating-a-merge-request-via-e-mail)
* [Reviewing and managing Merge Requests](#reviewing-and-managing-merge-requests)
# How to create a merge request[](#how-to-create-a-merge-request "Permalink")
在創建合并請求之前,請通讀"合并請求"的[簡介,](getting_started.html)以熟悉概念,術語并了解如何使用它們.
每個合并請求都從創建一個分支開始. 您可以通過[命令行](#new-merge-request-from-your-local-environment) ,Git CLI 應用程序或[GitLab UI](#new-merge-request-from-a-new-branch-created-through-the-ui)在本地進行操作.
本文檔介紹了創建合并請求的幾種方法.
啟動新的合并請求時,無論使用哪種方法,都將轉到" [**新合并請求"**頁面,](#new-merge-request-page)以在其中添加有關合并請求的信息.
如果將新分支推送到 GitLab,也不管使用哪種方法,都可以單擊[**Create Merge Request**](#create-merge-request-button)按鈕并從此處啟動合并請求.
## New Merge Request page[](#new-merge-request-page "Permalink")
在" **新合并請求"**頁面上,首先填寫**合并請求**的標題和描述. 如果分支上已經有提交,則標題將用第一條提交消息的第一行預填充,描述將用提交消息中的任何其他行預填充. 在所有情況下,標題都是唯一的必填字段.
在此處,您可以在其中填充信息(標題,描述,受讓人,里程碑,標簽,批準人),然后點擊**創建合并請求** .
在初始屏幕上,您還可以查看提交合并請求之前推送到分支的所有提交,管道和文件更改.
[](img/new_merge_request_page_v12_6.png)
**提示:**您可以在創建合并請求之前將一次或多次推送到 GitLab 中的分支.
## Create Merge Request button[](#create-merge-request-button "Permalink")
將新分支推送到 GitLab 后,請訪問 GitLab 中的存儲庫,并在屏幕頂??部看到一個號召性用語,您可以從中單擊**創建合并請求**按鈕.
[](img/create_merge_request_button_v12_6.png)
您還可以在以下頁面的右上方看到" **創建合并請求"**按鈕:
* **Project** page.
* **資料庫>文件** page.
* **合并請求** page.
In this case, GitLab will use the most recent branch you pushed changes to as the source branch, and the default branch in the current project as the target.
## New merge request by adding, editing, and uploading a file[](#new-merge-request-by-adding-editing-and-uploading-a-file "Permalink")
當您選擇通過 GitLab UI 編輯,添加或上傳文件時,在文件末尾,您會看到以下選項:添加**Commit 消息** ,選擇該**提交**的**Target 分支** ,然后選中**Start new**復選框. **具有這些更改的合并請求** .
同樣,如果通過 Web IDE 更改文件,則在左側邊欄中導航到" **提交"**時,將看到這些相同的選項.
添加,編輯或上傳文件后,請執行以下操作:
1. 在提交消息中描述您的更改.
2. 選擇一個現有分支以將您的提交添加到其中,或者,如果您想創建一個新分支,請鍵入新的分支名稱(不帶空格,大寫字母或特殊字符).
3. 保持選中復選框以立即開始新的合并請求,或者取消選中該復選框以在開始合并請求之前向該分支添加更多更改.
4. Click **提交變更**.
如果您選擇開始合并請求,則將轉到" [**新合并請求"**頁面](#new-merge-request-page) ,您可以在其中填寫信息并提交合并請求.
合并請求將針對存儲庫的默認分支. 如果要更改它,可以稍后通過編輯合并請求來進行更改.
## New merge request from a new branch created through the UI[](#new-merge-request-from-a-new-branch-created-through-the-ui "Permalink")
要通過 GitLab UI 快速開始處理文件,請導航至項目的" **存儲庫">"分支"** ,然后單擊" **新建分支"** . 將創建一個新分支,您可以開始編輯文件.
提交并推送后,您可以單擊" [**創建合并請求"**](#create-merge-request-button)按鈕以打開" [**新合并請求"**頁面](#new-merge-request-page) . 將使用當前分支作為源,并使用當前項目中的默認分支作為目標來啟動新的合并請求.
## New merge request from your local environment[](#new-merge-request-from-your-local-environment "Permalink")
假設您已將存儲庫克隆到計算機中,并且想要開始處理文件更改,請先創建并簽出一個新分支:
```
git checkout -b my-new-branch
```
處理文件更改,暫存并提交它們:
```
git add .
git commit -m "My commit message"
```
完成后, [將分支推送到 GitLab](../../../gitlab-basics/start-using-git.html#send-changes-to-gitlabcom) :
```
git push origin my-new-branch
```
在輸出中,GitLab 將提示您一個直接鏈接來創建合并請求:
```
...
remote: To create a merge request for docs-new-merge-request, visit:
remote: https://gitlab-instance.com/my-group/my-project/merge_requests/new?merge_request%5Bsource_branch%5D=my-new-branch
```
復制該鏈接并將其粘貼到瀏覽器中,將顯示" [**新合并請求"頁面**](#new-merge-request-page) .
在[通過命令行推送時](../push_options.html) , [還可以向命令添加](../push_options.html)一些[標志,](../push_options.html)以減少通過 UI 手動編輯合并請求的需要.
如果您沒有通過命令行將分支推送到 GitLab(例如,您使用 Git CLI 應用程序來推送更改),則可以通過單擊" [**創建合并請求"**](#create-merge-request-button)按鈕通過 GitLab UI [**創建合并請求**](#create-merge-request-button) .
## New merge request from an issue[](#new-merge-request-from-an-issue "Permalink")
您也可以[直接從 issue 創建一個新的合并請求](../repository/web_editor.html#create-a-new-branch-from-an-issue) .
## New merge request from the Merge Requests page[](#new-merge-request-from-the-merge-requests-page "Permalink")
您可以通過在項目中的" **合并請求"**頁面上單擊" **新建合并請求"**按鈕來開始創建新的合并請求. 然后選擇包含更改的源項目和分支,以及要將更改合并到的目標項目和分支. 單擊**比較分支,然后繼續**轉到" [**新合并請求"**頁面](#new-merge-request-page)并填寫詳細信息.
## New merge request from a fork[](#new-merge-request-from-a-fork "Permalink")
分叉項目并應用本地更改后,請完成以下步驟,從您的 fork 創建一個合并請求以貢獻回主項目:
1. 轉到**項目>您的項目,**然后選擇存儲庫的分支.
2. 在左側菜單中,轉到**合并請求** ,然后點擊**新建合并請求** .
3. 在" **源分支"**下拉列表框中,在分支的存儲庫中選擇您的分支作為源分支.
4. 在" **目標分支"**下拉列表框中,從上游存儲庫中選擇分支作為目標分支.
5. 輸入憑據后,單擊" **比較分支",然后繼續**將本地更改與上游存儲庫進行比較.
6. 分配用戶以查看您的更改,然后點擊**提交合并請求** .
合并更改后,您的更改將按照規范添加到上游存儲庫和分支中. 合并工作后,如果您不想對上游項目做出任何其他貢獻,則可以通過[刪除分支關系](../settings/index.html#removing-a-fork-relationship) ,在**Settings> Advanced Settings**部分[中將 fork 與](../settings/index.html#removing-a-fork-relationship)上游項目斷開鏈接.
有關更多詳細信息, [請參閱分叉工作流文檔](../repository/forking_workflow.html) .
## New merge request by email[](#new-merge-request-by-email-core-only "Permalink")
*要使用此功能,需要由 GitLab 管理員配置[傳入電子郵件](../../../administration/incoming_email.html)才能使用.* 它在 GitLab.com 中不可用.
您可以通過將電子郵件發送到特定于用戶的電子郵件地址來創建新的合并請求. 通過單擊**將新的合并請求**通過**電子郵件發送到該項目**按鈕,可以在合并請求頁面上獲取地址. 該主題將用作新合并請求的源分支名稱,而目標分支將是項目的默認分支. 消息正文(如果不為空)將用作合并請求描述. 您需要啟用["通過電子郵件回復"](../../../administration/reply_by_email.html)才能使用此功能. 如果您的實例未啟用它,則可以要求您的 GitLab 管理員這樣做.
這是一個私人電子郵件地址,僅為您生成. **將其保存在自己**手中,因為擁有它的任何人都可以像您一樣創建問題或合并請求. 您可以將此地址添加到您的聯系人列表中以便于訪問.
[](img/create_from_email.png)
*在 GitLab 11.7 中,我們更新了生成的電子郵件地址的格式. 但是,仍支持較舊的格式,從而允許現有別名或聯系人繼續工作.*
### Adding patches when creating a merge request via e-mail[](#adding-patches-when-creating-a-merge-request-via-e-mail "Permalink")
在 GitLab 11.5 中[引入](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/22723) .
您可以通過將補丁添加為電子郵件的附件,將提交添加到正在創建的合并請求中. 文件名以`.patch`結尾的所有附件都將被視為補丁程序,并將按名稱順序對其進行處理.
補丁的總大小可以是 2MB.
如果主題的源分支不存在,那么將從存儲庫的 HEAD 或指定的目標分支創建源分支以應用補丁. 可以使用[`/target_branch`快速操作](../quick_actions.html)指定目標分支. 如果源分支已經存在,則將在其頂部應用補丁.
## Reviewing and managing Merge Requests[](#reviewing-and-managing-merge-requests "Permalink")
提交合并請求后,可以通過 GitLab 進行[審查和管理](reviewing_and_managing_merge_requests.html) .
- GitLab Docs
- Installation
- Requirements
- GitLab cloud native Helm Chart
- Install GitLab with Docker
- Installation from source
- Install GitLab on Microsoft Azure
- Installing GitLab on Google Cloud Platform
- Installing GitLab on Amazon Web Services (AWS)
- Analytics
- Code Review Analytics
- Productivity Analytics
- Value Stream Analytics
- Kubernetes clusters
- Adding and removing Kubernetes clusters
- Adding EKS clusters
- Adding GKE clusters
- Group-level Kubernetes clusters
- Instance-level Kubernetes clusters
- Canary Deployments
- Cluster Environments
- Deploy Boards
- GitLab Managed Apps
- Crossplane configuration
- Cluster management project (alpha)
- Kubernetes Logs
- Runbooks
- Serverless
- Deploying AWS Lambda function using GitLab CI/CD
- Securing your deployed applications
- Groups
- Contribution Analytics
- Custom group-level project templates
- Epics
- Manage epics
- Group Import/Export
- Insights
- Issues Analytics
- Iterations
- Public access
- SAML SSO for GitLab.com groups
- SCIM provisioning using SAML SSO for GitLab.com groups
- Subgroups
- Roadmap
- Projects
- GitLab Secure
- Security Configuration
- Container Scanning
- Dependency Scanning
- Dependency List
- Static Application Security Testing (SAST)
- Secret Detection
- Dynamic Application Security Testing (DAST)
- GitLab Security Dashboard
- Offline environments
- Standalone Vulnerability pages
- Security scanner integration
- Badges
- Bulk editing issues and merge requests at the project level
- Code Owners
- Compliance
- License Compliance
- Compliance Dashboard
- Create a project
- Description templates
- Deploy Keys
- Deploy Tokens
- File finder
- Project integrations
- Integrations
- Atlassian Bamboo CI Service
- Bugzilla Service
- Custom Issue Tracker service
- Discord Notifications service
- Enabling emails on push
- GitHub project integration
- Hangouts Chat service
- Atlassian HipChat
- Irker IRC Gateway
- GitLab Jira integration
- Mattermost Notifications Service
- Mattermost slash commands
- Microsoft Teams service
- Mock CI Service
- Prometheus integration
- Redmine Service
- Slack Notifications Service
- Slack slash commands
- GitLab Slack application
- Webhooks
- YouTrack Service
- Insights
- Issues
- Crosslinking Issues
- Design Management
- Confidential issues
- Due dates
- Issue Boards
- Issue Data and Actions
- Labels
- Managing issues
- Milestones
- Multiple Assignees for Issues
- Related issues
- Service Desk
- Sorting and ordering issue lists
- Issue weight
- Associate a Zoom meeting with an issue
- Merge requests
- Allow collaboration on merge requests across forks
- Merge Request Approvals
- Browser Performance Testing
- How to create a merge request
- Cherry-pick changes
- Code Quality
- Load Performance Testing
- Merge Request dependencies
- Fast-forward merge requests
- Merge when pipeline succeeds
- Merge request conflict resolution
- Reverting changes
- Reviewing and managing merge requests
- Squash and merge
- Merge requests versions
- Draft merge requests
- Members of a project
- Migrating projects to a GitLab instance
- Import your project from Bitbucket Cloud to GitLab
- Import your project from Bitbucket Server to GitLab
- Migrating from ClearCase
- Migrating from CVS
- Import your project from FogBugz to GitLab
- Gemnasium
- Import your project from GitHub to GitLab
- Project importing from GitLab.com to your private GitLab instance
- Import your project from Gitea to GitLab
- Import your Jira project issues to GitLab
- Migrating from Perforce Helix
- Import Phabricator tasks into a GitLab project
- Import multiple repositories by uploading a manifest file
- Import project from repo by URL
- Migrating from SVN to GitLab
- Migrating from TFVC to Git
- Push Options
- Releases
- Repository
- Branches
- Git Attributes
- File Locking
- Git file blame
- Git file history
- Repository mirroring
- Protected branches
- Protected tags
- Push Rules
- Reduce repository size
- Signing commits with GPG
- Syntax Highlighting
- GitLab Web Editor
- Web IDE
- Requirements Management
- Project settings
- Project import/export
- Project access tokens (Alpha)
- Share Projects with other Groups
- Snippets
- Static Site Editor
- Wiki
- Project operations
- Monitor metrics for your CI/CD environment
- Set up alerts for Prometheus metrics
- Embedding metric charts within GitLab-flavored Markdown
- Embedding Grafana charts
- Using the Metrics Dashboard
- Dashboard YAML properties
- Metrics dashboard settings
- Panel types for dashboards
- Using Variables
- Templating variables for metrics dashboards
- Prometheus Metrics library
- Monitoring AWS Resources
- Monitoring HAProxy
- Monitoring Kubernetes
- Monitoring NGINX
- Monitoring NGINX Ingress Controller
- Monitoring NGINX Ingress Controller with VTS metrics
- Alert Management
- Error Tracking
- Tracing
- Incident Management
- GitLab Status Page
- Feature Flags
- GitLab CI/CD
- GitLab CI/CD pipeline configuration reference
- GitLab CI/CD include examples
- Introduction to CI/CD with GitLab
- Getting started with GitLab CI/CD
- How to enable or disable GitLab CI/CD
- Using SSH keys with GitLab CI/CD
- Migrating from CircleCI
- Migrating from Jenkins
- Auto DevOps
- Getting started with Auto DevOps
- Requirements for Auto DevOps
- Customizing Auto DevOps
- Stages of Auto DevOps
- Upgrading PostgreSQL for Auto DevOps
- Cache dependencies in GitLab CI/CD
- GitLab ChatOps
- Cloud deployment
- Docker integration
- Building Docker images with GitLab CI/CD
- Using Docker images
- Building images with kaniko and GitLab CI/CD
- GitLab CI/CD environment variables
- Predefined environment variables reference
- Where variables can be used
- Deprecated GitLab CI/CD variables
- Environments and deployments
- Protected Environments
- GitLab CI/CD Examples
- Test a Clojure application with GitLab CI/CD
- Using Dpl as deployment tool
- Testing a Phoenix application with GitLab CI/CD
- End-to-end testing with GitLab CI/CD and WebdriverIO
- DevOps and Game Dev with GitLab CI/CD
- Deploy a Spring Boot application to Cloud Foundry with GitLab CI/CD
- How to deploy Maven projects to Artifactory with GitLab CI/CD
- Testing PHP projects
- Running Composer and NPM scripts with deployment via SCP in GitLab CI/CD
- Test and deploy Laravel applications with GitLab CI/CD and Envoy
- Test and deploy a Python application with GitLab CI/CD
- Test and deploy a Ruby application with GitLab CI/CD
- Test and deploy a Scala application to Heroku
- GitLab CI/CD for external repositories
- Using GitLab CI/CD with a Bitbucket Cloud repository
- Using GitLab CI/CD with a GitHub repository
- GitLab Pages
- GitLab Pages
- GitLab Pages domain names, URLs, and baseurls
- Create a GitLab Pages website from scratch
- Custom domains and SSL/TLS Certificates
- GitLab Pages integration with Let's Encrypt
- GitLab Pages Access Control
- Exploring GitLab Pages
- Incremental Rollouts with GitLab CI/CD
- Interactive Web Terminals
- Optimizing GitLab for large repositories
- Metrics Reports
- CI/CD pipelines
- Pipeline Architecture
- Directed Acyclic Graph
- Multi-project pipelines
- Parent-child pipelines
- Pipelines for Merge Requests
- Pipelines for Merged Results
- Merge Trains
- Job artifacts
- Pipeline schedules
- Pipeline settings
- Triggering pipelines through the API
- Review Apps
- Configuring GitLab Runners
- GitLab CI services examples
- Using MySQL
- Using PostgreSQL
- Using Redis
- Troubleshooting CI/CD
- GitLab Package Registry
- GitLab Container Registry
- Dependency Proxy
- GitLab Composer Repository
- GitLab Conan Repository
- GitLab Maven Repository
- GitLab NPM Registry
- GitLab NuGet Repository
- GitLab PyPi Repository
- API Docs
- API resources
- .gitignore API
- GitLab CI YMLs API
- Group and project access requests API
- Appearance API
- Applications API
- Audit Events API
- Avatar API
- Award Emoji API
- Project badges API
- Group badges API
- Branches API
- Broadcast Messages API
- Project clusters API
- Group clusters API
- Instance clusters API
- Commits API
- Container Registry API
- Custom Attributes API
- Dashboard annotations API
- Dependencies API
- Deploy Keys API
- Deployments API
- Discussions API
- Dockerfiles API
- Environments API
- Epics API
- Events
- Feature Flags API
- Feature flag user lists API
- Freeze Periods API
- Geo Nodes API
- Group Activity Analytics API
- Groups API
- Import API
- Issue Boards API
- Group Issue Boards API
- Issues API
- Epic Issues API
- Issues Statistics API
- Jobs API
- Keys API
- Labels API
- Group Labels API
- License
- Licenses API
- Issue links API
- Epic Links API
- Managed Licenses API
- Markdown API
- Group and project members API
- Merge request approvals API
- Merge requests API
- Project milestones API
- Group milestones API
- Namespaces API
- Notes API
- Notification settings API
- Packages API
- Pages domains API
- Pipeline schedules API
- Pipeline triggers API
- Pipelines API
- Project Aliases API
- Project import/export API
- Project repository storage moves API
- Project statistics API
- Project templates API
- Projects API
- Protected branches API
- Protected tags API
- Releases API
- Release links API
- Repositories API
- Repository files API
- Repository submodules API
- Resource label events API
- Resource milestone events API
- Resource weight events API
- Runners API
- SCIM API
- Search API
- Services API
- Application settings API
- Sidekiq Metrics API
- Snippets API
- Project snippets
- Application statistics API
- Suggest Changes API
- System hooks API
- Tags API
- Todos API
- Users API
- Project-level Variables API
- Group-level Variables API
- Version API
- Vulnerabilities API
- Vulnerability Findings API
- Wikis API
- GraphQL API
- Getting started with GitLab GraphQL API
- GraphQL API Resources
- API V3 to API V4
- Validate the .gitlab-ci.yml (API)
- User Docs
- Abuse reports
- User account
- Active sessions
- Deleting a User account
- Permissions
- Personal access tokens
- Profile preferences
- Threads
- GitLab and SSH keys
- GitLab integrations
- Git
- GitLab.com settings
- Infrastructure as code with Terraform and GitLab
- GitLab keyboard shortcuts
- GitLab Markdown
- AsciiDoc
- GitLab Notification Emails
- GitLab Quick Actions
- Autocomplete characters
- Reserved project and group names
- Search through GitLab
- Advanced Global Search
- Advanced Syntax Search
- Time Tracking
- GitLab To-Do List
- Administrator Docs
- Reference architectures
- Reference architecture: up to 1,000 users
- Reference architecture: up to 2,000 users
- Reference architecture: up to 3,000 users
- Reference architecture: up to 5,000 users
- Reference architecture: up to 10,000 users
- Reference architecture: up to 25,000 users
- Reference architecture: up to 50,000 users
- Troubleshooting a reference architecture set up
- Working with the bundled Consul service
- Configuring PostgreSQL for scaling
- Configuring GitLab application (Rails)
- Load Balancer for multi-node GitLab
- Configuring a Monitoring node for Scaling and High Availability
- NFS
- Working with the bundled PgBouncer service
- Configuring Redis for scaling
- Configuring Sidekiq
- Admin Area settings
- Continuous Integration and Deployment Admin settings
- Custom instance-level project templates
- Diff limits administration
- Enable and disable GitLab features deployed behind feature flags
- Geo nodes Admin Area
- GitLab Pages administration
- Health Check
- Job logs
- Labels administration
- Log system
- PlantUML & GitLab
- Repository checks
- Repository storage paths
- Repository storage types
- Account and limit settings
- Service templates
- System hooks
- Changing your time zone
- Uploads administration
- Abuse reports
- Activating and deactivating users
- Audit Events
- Blocking and unblocking users
- Broadcast Messages
- Elasticsearch integration
- Gitaly
- Gitaly Cluster
- Gitaly reference
- Monitoring GitLab
- Monitoring GitLab with Prometheus
- Performance Bar
- Usage statistics
- Object Storage
- Performing Operations in GitLab
- Cleaning up stale Redis sessions
- Fast lookup of authorized SSH keys in the database
- Filesystem Performance Benchmarking
- Moving repositories managed by GitLab
- Run multiple Sidekiq processes
- Sidekiq MemoryKiller
- Switching to Puma
- Understanding Unicorn and unicorn-worker-killer
- User lookup via OpenSSH's AuthorizedPrincipalsCommand
- GitLab Package Registry administration
- GitLab Container Registry administration
- Replication (Geo)
- Geo database replication
- Geo with external PostgreSQL instances
- Geo configuration
- Using a Geo Server
- Updating the Geo nodes
- Geo with Object storage
- Docker Registry for a secondary node
- Geo for multiple nodes
- Geo security review (Q&A)
- Location-aware Git remote URL with AWS Route53
- Tuning Geo
- Removing secondary Geo nodes
- Geo data types support
- Geo Frequently Asked Questions
- Geo Troubleshooting
- Geo validation tests
- Disaster Recovery (Geo)
- Disaster recovery for planned failover
- Bring a demoted primary node back online
- Automatic background verification
- Rake tasks
- Back up and restore GitLab
- Clean up
- Namespaces
- Maintenance Rake tasks
- Geo Rake Tasks
- GitHub import
- Import bare repositories
- Integrity check Rake task
- LDAP Rake tasks
- Listing repository directories
- Praefect Rake tasks
- Project import/export administration
- Repository storage Rake tasks
- Generate sample Prometheus data
- Uploads migrate Rake tasks
- Uploads sanitize Rake tasks
- User management
- Webhooks administration
- X.509 signatures
- Server hooks
- Static objects external storage
- Updating GitLab
- GitLab release and maintenance policy
- Security
- Password Storage
- Custom password length limits
- Restrict allowed SSH key technologies and minimum length
- Rate limits
- Webhooks and insecure internal web services
- Information exclusivity
- How to reset your root password
- How to unlock a locked user from the command line
- User File Uploads
- How we manage the TLS protocol CRIME vulnerability
- User email confirmation at sign-up
- Security of running jobs
- Proxying assets
- CI/CD Environment Variables
- Contributor and Development Docs
- Contribute to GitLab
- Community members & roles
- Implement design & UI elements
- Issues workflow
- Merge requests workflow
- Code Review Guidelines
- Style guides
- GitLab Architecture Overview
- CI/CD development documentation
- Database guides
- Database Review Guidelines
- Database Review Guidelines
- Migration Style Guide
- What requires downtime?
- Understanding EXPLAIN plans
- Rake tasks for developers
- Mass inserting Rails models
- GitLab Documentation guidelines
- Documentation Style Guide
- Documentation structure and template
- Documentation process
- Documentation site architecture
- Global navigation
- GitLab Docs monthly release process
- Telemetry Guide
- Usage Ping Guide
- Snowplow Guide
- Experiment Guide
- Feature flags in development of GitLab
- Feature flags process
- Developing with feature flags
- Feature flag controls
- Document features deployed behind feature flags
- Frontend Development Guidelines
- Accessibility & Readability
- Ajax
- Architecture
- Axios
- Design Patterns
- Frontend Development Process
- DropLab
- Emojis
- Filter
- Frontend FAQ
- GraphQL
- Icons and SVG Illustrations
- InputSetter
- Performance
- Principles
- Security
- Tooling
- Vuex
- Vue
- Geo (development)
- Geo self-service framework (alpha)
- Gitaly developers guide
- GitLab development style guides
- API style guide
- Go standards and style guidelines
- GraphQL API style guide
- Guidelines for shell commands in the GitLab codebase
- HTML style guide
- JavaScript style guide
- Migration Style Guide
- Newlines style guide
- Python Development Guidelines
- SCSS style guide
- Shell scripting standards and style guidelines
- Sidekiq debugging
- Sidekiq Style Guide
- SQL Query Guidelines
- Vue.js style guide
- Instrumenting Ruby code
- Testing standards and style guidelines
- Flaky tests
- Frontend testing standards and style guidelines
- GitLab tests in the Continuous Integration (CI) context
- Review Apps
- Smoke Tests
- Testing best practices
- Testing levels
- Testing Rails migrations at GitLab
- Testing Rake tasks
- End-to-end Testing
- Beginner's guide to writing end-to-end tests
- End-to-end testing Best Practices
- Dynamic Element Validation
- Flows in GitLab QA
- Page objects in GitLab QA
- Resource class in GitLab QA
- Style guide for writing end-to-end tests
- Testing with feature flags
- Translate GitLab to your language
- Internationalization for GitLab
- Translating GitLab
- Proofread Translations
- Merging translations from CrowdIn
- Value Stream Analytics development guide
- GitLab subscription
- Activate GitLab EE with a license