# Import your project from GitHub to GitLab
> 原文:[https://docs.gitlab.com/ee/user/project/import/github.html](https://docs.gitlab.com/ee/user/project/import/github.html)
* [Overview](#overview)
* [How it works](#how-it-works)
* [Import your GitHub repository into GitLab](#import-your-github-repository-into-gitlab)
* [Using the GitHub integration](#using-the-github-integration)
* [Using a GitHub token](#using-a-github-token)
* [Selecting which repositories to import](#selecting-which-repositories-to-import)
* [Mirroring and pipeline status sharing](#mirroring-and-pipeline-status-sharing)
* [Improving the speed of imports on self-managed instances](#improving-the-speed-of-imports-on-self-managed-instances)
# Import your project from GitHub to GitLab[](#import-your-project-from-github-to-gitlab "Permalink")
使用導入器,您可以將 GitHub 存儲庫導入 GitLab.com 或自管理的 GitLab 實例.
## Overview[](#overview "Permalink")
**注意:**這些說明適用于 GitLab.com 上的用戶,但是如果您是自助 GitLab 實例的管理員,或者要從 GitHub Enterprise 導入,則必須啟用[GitHub 集成](../../../integration/github.html) . GitHub 集成是從 GitHub Enterprise 導入的唯一方法. 如果您使用的是 GitLab.com,則可以使用[個人訪問令牌](#using-a-github-token)導入 GitHub 存儲庫,但不建議使用此方法,因為該方法無法將所有用戶活動(例如問題和請求請求)與匹配的 GitLab 用戶相關聯. 如果您是自我管理的 GitLab 實例的管理員,則還可以使用[GitHub Rake 任務](../../../administration/raketasks/github_import.html)從 GitHub 導入項目,而不受 Sidekiq worker 的限制.
導入了項目的以下方面:
* 倉庫描述(GitLab.com&7.7+)
* Git 存儲庫數據(GitLab.com&7.7+)
* 問題(GitLab.com 和 7.7+)
* 拉取請求(GitLab.com&8.4+)
* Wiki 頁面(GitLab.com&8.4+)
* 里程碑(GitLab.com&8.7+)
* 標簽(GitLab.com 和 8.7+)
* 發行說明說明(GitLab.com 和 8.12+)
* 拉取請求評論評論(GitLab.com&10.2+)
* 定期發布和請求請求注釋
保留對拉取請求和問題的引用(GitLab.com&8.7+),并且每個導入的存儲庫都保持可見性級別,除非該[可見性級別受到限制](../../../public_access/public_access.html#restricting-the-use-of-public-or-internal-projects) ,在這種情況下,它默認為默認項目可見性.
## How it works[](#how-it-works "Permalink")
導入問題和請求請求時,導入程序會嘗試在 GitLab 實例的數據庫中查找其 GitHub 作者和受讓人(請注意,請求請求在 GitLab 中稱為"合并請求").
For this association to succeed, each GitHub author and assignee in the repository must meet one of the following conditions prior to the import:
* 以前使用 GitHub 圖標登錄到 GitLab 帳戶.
* 有一個 GitHub 帳戶,其[主要電子郵件地址](https://help.github.com/en/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address)與其 GitLab 帳戶的電子郵件地址匹配.
如果在 GitLab 的數據庫中未找到項目中引用的用戶,則將項目創建者(通常是啟動導入過程的用戶)設置為作者/受讓人,但是會添加關于該問題的注釋,其中提及原始 GitHub 作者.
如果不存在任何新的名稱空間(組),或者如果采用了名稱空間,則導入器會創建存儲庫,該存儲庫將在啟動導入過程的用戶的名稱空間下導入. 命名空間/存儲庫名稱也可以使用適當的權限進行編輯.
進口商還將在與未完成拉取請求相關的項目的分支上導入分支. 這些分支將以類似于`GH-SHA-username/pull-request-number/fork-name/branch`的命名方案導入. 與 GitHub 存儲庫相比,這可能導致分支中的差異.
有關更多技術細節,您可以參考[GitHub Importer](../../../development/github_importer.html "使用 GitHub 導入器")開發人員文檔.
有關導入過程的概述,請參閱[從 GitHub 遷移到 GitLab](https://youtu.be/VYOXuOg9tQI)的視頻.
## Import your GitHub repository into GitLab[](#import-your-github-repository-into-gitlab "Permalink")
### Using the GitHub integration[](#using-the-github-integration "Permalink")
在開始之前,請確保要映射到 GitLab 用戶的所有 GitHub 用戶都具有以下任一條件:
* 使用 GitHub 圖標登錄的 GitLab 帳戶-或-
* 一個 GitLab 帳戶,其電子郵件地址與 GitHub 用戶的[公共電子郵件地址](https://help.github.com/en/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address)匹配
用戶匹配嘗試將按該順序進行,并且如果兩種方法均未識別到用戶,則該活動將與執行導入的用戶帳戶相關聯.
**注意:**如果您使用的是自助式 GitLab 實例,或者要從 GitHub Enterprise 導入,則此過程要求您已配置[GitHub 集成](../../../integration/github.html) .
1. 在頂部導航欄中,單擊**+** ,然后選擇**新建項目** .
2. 選擇**導入項目**選項卡,然后選擇**GitHub** .
3. 選擇第一個按鈕以**列出您的 GitHub 存儲庫** . 您將被重定向到[GitHub 上](https://github.com)的頁面以授權 GitLab 應用程序.
4. 點擊**授權 gitlabhq** . 您將被重定向回 GitLab 的 Import 頁面,并列出所有 GitHub 存儲庫.
5. 繼續[選擇要導入的存儲庫](#selecting-which-repositories-to-import) .
### Using a GitHub token[](#using-a-github-token "Permalink")
**注意:**不建議使用個人訪問令牌導入項目. 如果您是 GitLab.com 用戶,則可以使用個人訪問令牌從 GitHub 導入項目,但是該方法無法將所有用戶活動(例如問題和請求請求)與匹配的 GitLab 用戶關聯. 如果您是自我管理的 GitLab 實例的管理員,或者要從 GitHub Enterprise 導入,則不能使用個人訪問令牌. 建議所有用戶使用[GitHub 集成方法(上述)](#using-the-github-integration) . 在" [如何工作"](#how-it-works)部分中了解更多信息.
如果您不使用 GitHub 集成,則仍可以通過 GitHub 執行授權以授予 GitLab 訪問您的存儲庫的權限:
1. 轉到[https://github.com/settings/tokens/new](https://github.com/settings/tokens/new)
2. 輸入令牌描述.
3. 選擇回購范圍??.
4. Click **生成令牌**.
5. 復制令牌哈希.
6. 返回到 GitLab 并將令牌提供給 GitHub 導入器.
7. 點擊**列出您的 GitHub 存儲庫**按鈕,并等待 GitLab 讀取您的存儲庫信息. 完成后,將帶您到導入器頁面以選擇要導入的存儲庫.
### Selecting which repositories to import[](#selecting-which-repositories-to-import "Permalink")
在授權訪問 GitHub 存儲庫后,您將重定向到 GitHub 導入程序頁面,并列出 GitHub 存儲庫.
1. 默認情況下,建議的存儲庫名稱空間與 GitHub 中存在的名稱匹配,但是根據您的權限,您可以選擇在繼續導入任何名稱之前編輯這些名稱.
2. 選擇任意數量的存儲庫旁邊的**導入**按鈕,或選擇**導入所有存儲庫** . 此外,您可以按名稱過濾項目. 如果應用了過濾器,則" **導入所有存儲庫"**僅導入匹配的存儲庫.
3. " **狀態"**列顯示每個存儲庫的導入狀態. 您可以選擇讓頁面保持打開狀態,它將實時更新,也可以稍后返回.
4. 導入存儲庫后,單擊其 GitLab 路徑以打開其 GitLab URL.
[](img/import_projects_from_github_importer_v12_3.png)
## Mirroring and pipeline status sharing[](#mirroring-and-pipeline-status-sharing "Permalink")
根據您的 GitLab 層,可以設置[項目鏡像](../repository/repository_mirroring.html) ,以使導入的項目與其 GitHub 副本保持同步.
此外,您可以配置 GitLab 以通過[GitHub Project Integration](../integrations/github.html)將管道狀態更新發送回 GitHub.
如果使用[CI / CD 作為外部存儲庫](../../../ci/ci_cd_for_external_repos/index.html)導入項目,則會自動配置以上兩項.
## Improving the speed of imports on self-managed instances[](#improving-the-speed-of-imports-on-self-managed-instances "Permalink")
**注意:**必須具有對 GitLab 服務器的管理員訪問權限.
對于大型項目,可能需要一段時間才能導入所有數據. 為了減少必要的時間,您可以增加處理以下隊列的 Sidekiq 工作程序的數量:
* `github_importer`
* `github_importer_advance_stage`
For an optimal experience, it’s recommended having at least 4 Sidekiq processes (each running a number of threads equal to the number of CPU cores) that *only* process these queues. It’s also recommended that these processes run on separate servers. For 4 servers with 8 cores this means you can import up to 32 objects (e.g., issues) in parallel.
減少克隆存儲庫所花費的時間可以通過增加存儲 Git 存儲庫(適用于您的 GitLab 實例)的磁盤的網絡吞吐量,CPU 容量和磁盤性能(例如,使用高性能 SSD)來完成. 增加 Sidekiq 工作人員的數量*不會*減少克隆存儲庫所花費的時間.
- 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