[{"data":1,"prerenderedAt":880},["ShallowReactive",2],{"/topics/version-control/software-team-collaboration":3,"navigation-en-us":182,"banner-en-us":617,"footer-en-us":625,"next-steps-en-us":870},{"id":4,"title":5,"body":6,"category":6,"config":6,"content":7,"description":6,"extension":174,"meta":175,"navigation":176,"path":177,"seo":178,"slug":6,"stem":180,"testContent":6,"type":6,"__hash__":181},"pages/en-us/topics/version-control/software-team-collaboration/index.yml","",null,[8,22,30,124,146,172],{"type":9,"componentName":9,"componentContent":10},"CommonBreadcrumbs",{"crumbs":11},[12,16,20],{"title":13,"config":14},"Topics",{"href":15},"/topics/",{"title":17,"config":18},"Version control",{"href":19},"/topics/version-control/",{"title":21},"Software team collaboration",{"type":23,"componentName":23,"componentContent":24},"CommonArticleHero",{"title":25,"text":26,"config":27},"What are software team collaboration best practices?","Software team collaboration is the combination of processes, tools, and practices that helps cross-functional teams deliver software reliably and faster. This guide covers five practical areas—communication, tools, documentation, feedback, and leadership—with concrete steps your team can implement today.\n",{"id":28,"twoColumns":29},"what-are-software-team-collaboration-best-practices?",false,{"type":31,"componentName":31,"componentContent":32},"CommonSideNavigationWithTree",{"anchors":33,"components":68},{"text":34,"data":35},"On this page",[36,40,44,48,52,56,60,64],{"config":37,"text":39},{"href":38},"#quick-definition","Quick definition",{"text":41,"config":42},"Communicate openly",{"href":43},"#communicate-openly",{"text":45,"config":46},"Select the right tools",{"href":47},"#select-the-right-tools",{"text":49,"config":50},"Write comprehensive documentation",{"href":51},"#write-comprehensive-documentation",{"text":53,"config":54},"Provide fast feedback",{"href":55},"#provide-fast-feedback",{"text":57,"config":58},"Lead effectively",{"href":59},"#lead-effectively",{"config":61,"text":63},{"href":62},"#best-practices-checklist","Quick checklist: collaboration best practices",{"text":65,"config":66},"GitLab features that accelerate collaboration",{"href":67},"#acceleration-features",[69,76,82,88,94,100,106,111,116],{"type":70,"componentName":70,"componentContent":71},"TopicsCopy",{"text":72,"config":73,"header":75},"Software team collaboration is the processes, tools, and behaviors that help cross-functional teams plan, build, review, and deliver software reliably.\n\nEffective collaboration makes decisions visible, reduces handoff delays, and gives developers, product managers, designers, QA professionals, security teams, and operations teams a shared view of the work.\n",{"id":74},"quick-definition","Quick definition: What is software team collaboration?",{"type":70,"componentName":70,"componentContent":77},{"header":78,"text":79,"config":80},"How to communicate openly?","Open communication helps teams share context, challenge assumptions, and surface problems before they become expensive to fix. It also helps break down information silos between development, operations, security, product, and business teams.\n\nCollaborative software development is founded on trust and transparency. Team members should be able to contribute ideas, question decisions, and provide feedback regardless of their role, location, or experience level.\n\n### Use asynchronous communication\n\n[Asynchronous communication](https://handbook.gitlab.com/handbook/company/culture/all-remote/asynchronous/) lets contributors participate across time zones and return to a discussion after they have had time to consider the options. It is useful for distributed teams, hybrid teams, and office-based teams alike.\n\nUse asynchronous communication for requirements, status updates, design proposals, decisions, and questions that do not require an immediate conversation. Record the outcome in the relevant issue, merge request, or project documentation so that people who were not in the original conversation can still understand the context.\n\nA useful team protocol should define:\n\n* Where requirements and decisions are recorded.\n\n* Which discussions need a live meeting.\n\n* How quickly contributors should respond to urgent requests.\n\n* How decisions are summarized after a meeting.\n\n* How unresolved questions are assigned and followed up.\n\n### Challenge assumptions\n\nGroupthink can cause teams to accept a solution before they have considered the alternatives. Invite contributors to question requirements, identify risks, and explain different perspectives before the team commits to an approach.\n\nFocus the discussion on the problem and the evidence rather than on who proposed the idea. Asking thoughtful questions helps teams identify problems earlier, learn from experienced contributors, and make decisions that are easier to revisit later.\n\n### Run retrospectives\n\nA retrospective gives the team a structured time to discuss what went well, what created friction, and what should change. Hold one after a release, project milestone, or incident while the details are still fresh.\n\nKeep the discussion focused on learning rather than blame. End with a small number of specific actions, assign an owner to each action, and review progress at the next planning session.\n",{"id":81},"communicate-openly",{"type":70,"componentName":70,"componentContent":83},{"header":84,"text":85,"config":86},"How to select the right tools?","Select tools that reduce handoffs and automate repeatable work. Start by enabling integrated CI/CD, automated security scanning, and a shared source of truth for issues, documentation, and decisions.\n\nThe right tools connect contributors across the software lifecycle, from [version control](/topics/version-control/) and code review to CI/CD, security, and delivery, so developers, QA, security professionals, product managers, designers, and team leads can collaborate with visibility into work and progress. They should reduce context switching rather than create another set of disconnected systems to maintain.\n\n### Automate repeatable work\n\nAutomation reduces manual tasks and the likelihood of human error. Start by identifying work that is repetitive, easy to standardize, or frequently forgotten during a release.\n\nExamples include building and testing code, checking dependencies, packaging artifacts, updating environments, and notifying reviewers. Automation should provide useful feedback without hiding the result from the people responsible for the change.\n\n### Use integrated CI/CD\n\n[Continuous integration and continuous delivery (CI/CD)](/topics/ci-cd/) help teams build, test, and deliver software through a repeatable workflow. Run automated checks when a merge request is opened or updated so the author and reviewers can see whether the change is ready to proceed.\n\nStart with a small pipeline that builds the project and runs the most important tests. Add additional checks as the team understands where failures occur and which feedback helps contributors make better decisions.\n\n### Build security into the workflow\n\nSecurity is a shared responsibility across the software lifecycle. Finding vulnerabilities late can force developers to revisit code they have not touched for months and delay a release.\n\nUse [application security testing](/solutions/application-security-testing/) to identify risks earlier in development. Depending on the application and team requirements, this may include static application security testing, dynamic application security testing, dependency scanning, container scanning, secret detection, and license compliance.\n\nDefine how the team responds to findings. For example, require high-severity findings to be resolved or explicitly approved before a change merges, while documenting how lower-risk findings are prioritized.\n\n### Connect project management and delivery\n\nProject management tools help teams plan releases, clarify requirements, identify stakeholders, and keep complex work visible. Use issues or work items to define the problem, record decisions, and link the resulting code changes and reviews.\n\n[GitLab issues](https://docs.gitlab.com/user/project/issues/) and related planning features can help teams keep delivery context connected to the work being completed.\n\n",{"id":87},"select-the-right-tools",{"type":70,"componentName":70,"componentContent":89},{"header":90,"text":91,"config":92},"How to write comprehensive documentation?","As teams grow and applications become more complex, documentation helps contributors understand processes, decisions, tools, and responsibilities without relying on meetings or individual memory.\n\nDocument workflows, branching strategies, release procedures, communication expectations, onboarding information, and decisions that other contributors may need to revisit. Documentation is most useful when it is maintained as part of the team’s normal workflow rather than written once and forgotten.\n\n### Maintain a single source of truth\n\nChoose a clear location for each type of information. A single source of truth reduces the risk of maintaining several incomplete or conflicting versions of the same process.\n\nMake ownership visible and review important documentation when the related workflow changes. Link documentation from issues, merge requests, project templates, and onboarding material so contributors can find it where they work.\n\n### Use project wikis\n\nA [project wiki](https://docs.gitlab.com/user/project/wiki/) can provide a shared space for project-specific processes, technical decisions, troubleshooting guidance, and team agreements. Use a consistent structure so contributors know where to find information.\n\nUseful wiki sections may include:\n\n* Project overview and ownership.\n\n* Development and local setup instructions.\n\n* Branching and merge request guidelines.\n\n* Testing and release procedures.\n\n* Security and incident response guidance.\n\n* Frequently asked questions and troubleshooting notes.\n\n\n### Document decisions and branching strategy\n\nRecord not only what the team decided, but also why. Decision records help future contributors understand the constraints, alternatives, and trade-offs behind an implementation.\n\nDocument the branching strategy in the same place. Include branch naming, review requirements, required checks, release branches, and the process for handling urgent fixes.\n\n",{"id":93},"write-comprehensive-documentation",{"type":70,"componentName":70,"componentContent":95},{"header":96,"text":97,"config":98},"How to provide fast feedback?","Provide feedback rapidly and in context: require merge request reviews, set a response target for reviewers, and use CI to run automated checks before human review. A 48-hour response target is a suggested starting point, not a universal policy; validate it against your team’s time zones, release cadence, and service-level expectations.\n\nFeedback is most useful when it focuses on the work, its impact on customers and business value, and the next action required. Make expectations clear so contributors know when feedback is needed and how to respond to it.\n\n### Use code reviews to share knowledge\n\nRegular [code reviews](/topics/version-control/what-is-code-review/) help teams find bugs earlier, share knowledge, improve code quality, and identify security or compliance concerns before changes reach customers.\n\nReviewers should explain the reasoning behind a requested change and distinguish between:\n\n* **Required changes:** Issues that must be addressed before the change can merge.\n\n* **Suggestions:** Improvements that are useful but not necessary for this change.\n\n* **Questions:** Points where the reviewer needs more context.\n\n* **Alternative approaches:** Different ways to solve the problem that may be worth discussing.\n\nReview every contributor’s work consistently, regardless of experience or role. Keep reviews focused by limiting the size of changes where possible and requesting clarification when the scope is difficult to understand.\n\n### Run automated checks before human review\n\nAutomated builds, tests, code quality checks, and security scans should provide initial feedback before reviewers spend time on detailed analysis. This lets reviewers focus on design, maintainability, risk, and business behavior rather than issues that automation can detect consistently.\n\nMake failures actionable. The pipeline should show what failed, where it failed, and what the contributor can do next.\n\n### Use pair programming when it adds value\n\nPair programming can help contributors solve complex problems, learn unfamiliar systems, and receive immediate feedback. It is particularly useful when a task crosses team boundaries, carries significant risk, or provides a learning opportunity.\n\nUse pairing selectively rather than requiring it for every task. Combine it with documentation and code review so knowledge remains accessible to the wider team.\n\n",{"id":99},"provide-fast-feedback",{"type":70,"componentName":70,"componentContent":101},{"header":102,"text":103,"config":104},"How to lead effectively?","Strong leadership sets the tone for collaboration. Managers and technical leaders should create an environment where contributors can experiment, raise concerns, challenge decisions, and learn from failure without fear of blame.\n\n### Identify roadblocks\n\nAsk contributors where work is waiting or being repeated. Common roadblocks include unclear ownership, slow reviews, missing environments, unreliable tests, manual release steps, and fragmented documentation.\n\nUse team feedback and delivery data to identify which problems have the greatest effect on progress. Then remove or reduce the most important source of friction rather than adding process to every part of the workflow.\n\n### Model collaborative behavior\n\nLeaders should demonstrate the behavior they expect from the team. Share context, document decisions, acknowledge uncertainty, ask for feedback, and explain how disagreements are resolved.\n\nReaching across the development lifecycle to learn from other contributors shows that collaboration is part of everyone’s role, not an activity delegated to a single team.\n\n### Create a blameless environment\n\nTeams are more likely to surface risks and experiment with better solutions when they can discuss mistakes without fear of personal blame. Focus incident and retrospective conversations on systems, decisions, and contributing factors.\n\nA blameless environment does not remove accountability. It makes it safer to share information early so the team can fix problems and improve the workflow.\n\n",{"id":105},"lead-effectively",{"type":70,"componentName":70,"componentContent":107},{"header":63,"config":108,"text":110},{"id":109},"best-practices-checklist","* Document team roles and the branching strategy in the project wiki.\n\n* Use issues or work items as the source of truth for requirements and decisions.\n\n* Default to asynchronous updates for context that does not require a live meeting.\n\n* Require merge request reviews before changes merge into the main branch.\n\n* Set and publish a reviewer response target that the team can consistently meet.\n\n* Run automated builds and tests for every merge request.\n\n* Run appropriate security scans before merging and define how findings are handled.\n\n* Link code changes, reviews, tests, and release decisions to the work item.\n\n* Hold a retrospective after each major release or delivery milestone.\n\n* Assign an owner and due date to every retrospective action.\n\n* Track one collaboration signal, such as review wait time or cycle time, and review it regularly.\n",{"type":70,"componentName":70,"componentContent":112},{"header":65,"text":113,"config":114},"GitLab connects planning, source code management, code review, CI/CD, security, documentation, and AI-assisted development in a shared workflow. Use these capabilities to support the collaboration practices described above.\n\n* **Issues and work items:** Plan work, capture requirements, and keep decisions connected to the work being delivered. See the [GitLab issues documentation](https://docs.gitlab.com/user/project/issues/).\n\n* **Merge requests and code review:** Discuss changes in context, request reviewers, and use approvals to support consistent review workflows. Learn [what code review is](/topics/version-control/what-is-code-review/).\n\n* **Integrated CI/CD:** Build, test, and deliver changes through automated pipelines so teams receive feedback before release. Explore [CI/CD](/topics/ci-cd/).\n\n* **Security testing:** Add security checks to the development workflow and surface findings where teams are already reviewing changes. Explore [application security testing](/solutions/application-security-testing/).\n\n* **Project wikis:** Maintain project-specific processes, onboarding information, branching guidance, and decisions in a shared documentation space. See [project wikis](https://docs.gitlab.com/user/project/wiki/).\n\n* **Code Suggestions:** Help developers generate and complete code, write tests, and stay in their development flow with [GitLab Duo Code Suggestions](/gitlab-duo-agent-platform/).\n\n* **Duo Agent Platform:** Coordinate AI-assisted work across software lifecycle tasks with [GitLab Duo Agent Platform](/gitlab-duo-agent-platform/).\n",{"id":115},"acceleration-features",{"type":117,"componentName":117,"componentContent":118},"TopicsCallToAction",{"subtitle":119,"primaryButton":120},"Learn how to collaborate without boundaries to unlock faster delivery with GitLab",{"text":121,"config":122},"Learn more",{"href":123},"/solutions/source-code-management/",{"type":125,"componentName":125,"componentContent":126},"CommonFaq",{"header":127,"groups":128},"Frequently Asked Questions",[129],{"questions":130},[131,134,137,140,143],{"question":132,"answer":133},"What are the most important software team collaboration best practices?","The five key practices are: communicate openly using asynchronous methods and retrospectives, select the right tools including automation and integrated CI/CD, write comprehensive documentation as a single source of truth, provide fast feedback through code reviews and pair programming, and lead effectively by modeling collaborative behavior and identifying roadblocks.",{"question":135,"answer":136},"How can software teams communicate effectively without constant meetings?","Teams should adopt asynchronous communication, which allows contributors to participate across time zones and respond when they've had time to reflect. This approach helps team members prioritize their workloads while ensuring no one misses important conversations due to scheduling conflicts.",{"question":138,"answer":139},"What tools should software development teams use to improve collaboration?","Teams should use integrated tools that include automation to reduce manual tasks, comprehensive security testing (SAST, DAST, dependency scanning), integrated CI/CD to identify errors early, and project management features like Kanban boards, issues, and epics to increase visibility and keep projects on track.",{"question":141,"answer":142},"Why is documentation important for software team collaboration?","Comprehensive documentation creates a single source of truth that preserves decisions and processes, helps developers learn and retrieve information, and ensures visibility across the team. It allows team members to self-serve information and understand the reasoning behind solutions without requiring meetings.",{"question":144,"answer":145},"How should code reviews be conducted to strengthen collaboration?","Code reviews should be a regular part of the workflow for every team member regardless of experience level. Reviewers should clearly communicate which changes are necessary, non-mandatory, or alternative solutions, explaining the reasoning behind each suggestion to provide feedback and insight.",{"type":147,"componentName":147,"componentContent":148},"CommonResourcesContainer",{"header":149,"tabs":150},"Want to learn more about collaborative software development?",[151],{"name":152,"items":153,"config":171},"resources",[154,163],{"header":155,"type":156,"image":157,"link":160},"How to collaborate without boundaries to unlock faster delivery with GitLab","Webcast",{"altText":155,"config":158},{"src":159},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1749159277/Website/Topics/resources_20.jpg",{"text":121,"config":161},{"href":162,"icon":156,"modal":29},"/events/",{"header":164,"type":156,"image":165,"link":168},"Discover how code review and source code management streamline collaboration",{"altText":164,"config":166},{"src":167},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1749157558/Website/Topics/resources_11.jpg",{"text":121,"config":169},{"href":170,"icon":156,"modal":29},"https://page.gitlab.com/resources-demo-scm.html",{"key":152},{"type":173,"componentName":173},"CommonNextSteps","yml",{},true,"/en-us/topics/version-control/software-team-collaboration",{"title":25,"ogTitle":25,"description":179,"ogDescription":179},"Successful software projects require effective team collaboration across the entire development lifecycle.","en-us/topics/version-control/software-team-collaboration/index","fwJLH9ieg64KsAEEaHYYWGF4M8gk-R6T_6WU-7CkWWk",{"logo":183,"freeTrial":188,"sales":193,"login":198,"items":203,"search":536,"minimal":568,"duo":587,"switchNav":596,"pricingDeployment":607},{"config":184},{"href":185,"dataGaName":186,"dataGaLocation":187},"/","gitlab logo","header",{"text":189,"config":190},"Get free trial",{"href":191,"dataGaName":192,"dataGaLocation":187},"https://gitlab.com/-/trial_registrations/new?glm_source=about.gitlab.com&glm_content=default-saas-trial/","free trial",{"text":194,"config":195},"Request a demo",{"href":196,"dataGaName":197,"dataGaLocation":187},"/request-a-demo/","sales",{"text":199,"config":200},"Sign in",{"href":201,"dataGaName":202,"dataGaLocation":187},"https://gitlab.com/users/sign_in/","sign in",[204,289,377,382,460,514],{"text":205,"left":176,"config":206,"menu":208},"Platform",{"dataNavLevelOne":207},"platform",{"type":209,"link":210,"columns":214,"feature":278},"lists",{"text":211,"config":212},"Explore the Platform",{"href":213,"dataGaName":207,"dataGaLocation":187},"/platform/",[215,237,260],{"title":216,"items":217},"DevOps",[218,223,227,232],{"text":219,"config":220},"CI/CD",{"href":221,"dataGaLocation":187,"dataGaName":222},"/solutions/continuous-integration/","ci/cd",{"text":224,"config":225},"Source Code Management",{"href":123,"dataGaLocation":187,"dataGaName":226},"source code management",{"text":228,"config":229},"Agile Delivery",{"href":230,"dataGaLocation":187,"dataGaName":231},"/solutions/agile-delivery/","agile delivery",{"text":233,"config":234},"Artifact Management",{"href":235,"dataGaLocation":187,"dataGaName":236},"/artifact-central/","artifact management",{"title":238,"items":239},"Security & Governance",[240,245,250,255],{"text":241,"config":242},"Application Security Testing",{"href":243,"dataGaLocation":187,"dataGaName":244},"/solutions/application-security-testing/","application security testing",{"text":246,"config":247},"Governance & Compliance",{"href":248,"dataGaLocation":187,"dataGaName":249},"/solutions/software-compliance/","governance and compliance",{"text":251,"config":252},"Secrets Management",{"href":253,"dataGaLocation":187,"dataGaName":254},"/gitlab-secrets-manager/","secrets management",{"text":256,"config":257},"Supply Chain Security",{"href":258,"dataGaLocation":187,"dataGaName":259},"/solutions/supply-chain/","supply chain security",{"title":261,"items":262},"Agentic AI & Context",[263,268,273],{"text":264,"config":265},"Duo Agent Platform",{"href":266,"dataGaLocation":187,"dataGaName":267},"/gitlab-duo-agent-platform/","duo agent platform",{"text":269,"config":270},"Orbit Context Graph",{"href":271,"dataGaLocation":187,"dataGaName":272},"/gitlab-orbit/","orbit",{"text":274,"config":275},"Visibility & Measurement",{"href":276,"dataGaLocation":187,"dataGaName":277},"/solutions/visibility-measurement/","visibility and measurement",{"config":279,"title":282,"text":283,"link":284},{"background":280,"textColor":281},"url('https://res.cloudinary.com/about-gitlab-com/image/upload/v1790185102/o7dn32anqcb6z8dgd3as.jpg')","#000","GitLab Orbit is generally available","Higher agent accuracy, lower token cost",{"text":285,"config":286},"Read the announcement",{"href":287,"dataGaName":288,"dataGaLocation":187},"/blog/gitlab-orbit-ga/","orbit ga announcement",{"text":290,"left":176,"config":291,"menu":293},"Solutions",{"dataNavLevelOne":292},"solutions",{"type":209,"link":294,"columns":298,"feature":368},{"text":295,"config":296},"View all Solutions",{"href":297,"dataGaName":292,"dataGaLocation":187},"/solutions/",[299,317,335],{"title":300,"items":301},"Outcomes",[302,307,312],{"text":303,"config":304},"DevOps Modernization",{"href":305,"dataGaLocation":187,"dataGaName":306},"/assessments/devops-modernization-assessment/","devops modernization",{"text":308,"config":309},"Security Modernization",{"href":310,"dataGaLocation":187,"dataGaName":311},"/assessments/security-modernization-assessment/","security modernization",{"text":313,"config":314},"AI Modernization",{"href":315,"dataGaLocation":187,"dataGaName":316},"/assessments/ai-modernization-assessment/","ai modernization",{"title":318,"items":319},"By size",[320,325,330],{"text":321,"config":322},"Enterprise",{"href":323,"dataGaLocation":187,"dataGaName":324},"/enterprise/","enterprise",{"text":326,"config":327},"Small Business",{"href":328,"dataGaLocation":187,"dataGaName":329},"/small-business/","small business",{"text":331,"config":332},"Startups",{"href":333,"dataGaLocation":187,"dataGaName":334},"/solutions/startups/","startups",{"title":336,"items":337},"Industries",[338,343,348,353,358,363],{"text":339,"config":340},"Financial Services",{"href":341,"dataGaLocation":187,"dataGaName":342},"/solutions/finance/","financial services",{"text":344,"config":345},"Public Sector",{"href":346,"dataGaLocation":187,"dataGaName":347},"/solutions/public-sector/","public sector",{"text":349,"config":350},"Telecommunications",{"href":351,"dataGaLocation":187,"dataGaName":352},"/solutions/telecommunications/","telecommunications",{"text":354,"config":355},"Automotive",{"href":356,"dataGaLocation":187,"dataGaName":357},"/solutions/automotive/","automotive",{"text":359,"config":360},"Education",{"href":361,"dataGaLocation":187,"dataGaName":362},"/solutions/education/","education",{"text":364,"config":365},"Aerospace",{"href":366,"dataGaLocation":187,"dataGaName":367},"/solutions/aerospace/","aerospace",{"config":369,"title":370,"text":371,"link":372},{"background":280,"textColor":281},"GitLab Security Standard","Learn how to harden your software factory and let AI agents earn autonomy, without trading away security.",{"text":373,"config":374},"Explore the standard",{"href":375,"dataGaName":376,"dataGaLocation":187},"/gitlab-security-standard/","gitlab security standard",{"text":378,"config":379},"Pricing",{"href":380,"dataGaName":381,"dataGaLocation":187,"dataNavLevelOne":381},"/pricing/","pricing",{"text":383,"config":384,"menu":385},"Resources",{"dataNavLevelOne":152},{"type":209,"link":386,"columns":390,"feature":451},{"text":387,"config":388},"View all resources",{"href":389,"dataGaName":152,"dataGaLocation":187},"/resources/",[391,424],{"title":392,"items":393},"Discover",[394,399,404,409,414,419],{"text":395,"config":396},"Docs",{"href":397,"dataGaName":398,"dataGaLocation":187},"https://docs.gitlab.com/","docs",{"text":400,"config":401},"University",{"href":402,"dataGaName":403,"dataGaLocation":187},"https://university.gitlab.com/","university",{"text":405,"config":406},"Demo Series",{"href":407,"dataGaName":408,"dataGaLocation":187},"/gitlab-technical-demo-series/","demo series",{"text":410,"config":411},"Demo Hub",{"href":412,"dataGaName":413,"dataGaLocation":187},"/demo-hub/","demo hub",{"text":415,"config":416},"Services",{"href":417,"dataGaName":418,"dataGaLocation":187},"/services/","services",{"text":420,"config":421},"Well Architected",{"href":422,"dataGaName":423,"dataGaLocation":187},"/resources/well-architected/","well architected",{"title":425,"items":426},"Connect",[427,432,437,442,447],{"text":428,"config":429},"Blog",{"href":430,"dataGaName":431,"dataGaLocation":187},"/blog/","blog",{"text":433,"config":434},"Community",{"href":435,"dataGaName":436,"dataGaLocation":187},"/community/","community",{"text":438,"config":439},"Customers",{"href":440,"dataGaName":441,"dataGaLocation":187},"/customers/","customers",{"text":443,"config":444},"Partners",{"href":445,"dataGaName":446,"dataGaLocation":187},"/partners/","partners",{"text":448,"config":449},"Events",{"href":162,"dataGaName":450,"dataGaLocation":187},"events",{"config":452,"title":453,"text":454,"link":455},{"background":280,"textColor":281},"What’s new in GitLab","Stay updated with our latest features and improvements.",{"text":456,"config":457},"Read the latest",{"href":458,"dataGaName":459,"dataGaLocation":187},"/whats-new/","whats new",{"text":461,"config":462,"menu":464},"Company",{"dataNavLevelOne":463},"company",{"type":209,"columns":465},[466],{"items":467},[468,473,479,484,489,494,499,504,509],{"text":469,"config":470},"About",{"href":471,"dataGaName":472,"dataGaLocation":187},"/company/","about",{"text":474,"config":475,"footerGa":478},"Jobs",{"href":476,"dataGaName":477,"dataGaLocation":187},"/jobs/","jobs",{"dataGaName":477},{"text":480,"config":481},"Press",{"href":482,"dataGaName":483,"dataGaLocation":187},"/press/","press",{"text":485,"config":486},"Handbook",{"href":487,"dataGaName":488,"dataGaLocation":187},"https://handbook.gitlab.com/","handbook",{"text":490,"config":491},"Leadership",{"href":492,"dataGaName":493,"dataGaLocation":187},"/company/team/e-group/","leadership",{"text":495,"config":496},"Investor relations",{"href":497,"dataGaName":498,"dataGaLocation":187},"https://ir.gitlab.com/overview/default.aspx","investor relations",{"text":500,"config":501},"Trust Center",{"href":502,"dataGaName":503,"dataGaLocation":187},"/security/","trust center",{"text":505,"config":506},"AI Transparency Center",{"href":507,"dataGaName":508,"dataGaLocation":187},"/ai-transparency-center/","ai transparency center",{"text":510,"config":511},"Newsletter",{"href":512,"dataGaName":513,"dataGaLocation":187},"/company/contact/#contact-forms","newsletter",{"text":515,"config":516,"menu":517},"Contact us",{"dataNavLevelOne":463},{"type":209,"columns":518},[519],{"items":520},[521,526,531],{"text":522,"config":523},"Talk to sales",{"href":524,"dataGaName":525,"dataGaLocation":187},"/sales/","talk to sales",{"text":527,"config":528},"Support portal",{"href":529,"dataGaName":530,"dataGaLocation":187},"https://support.gitlab.com/hc/en-us","support portal",{"text":532,"config":533},"Customer portal",{"href":534,"dataGaName":535,"dataGaLocation":187},"https://customers.gitlab.com/customers/sign_in/","customer portal",{"close":537,"login":538,"suggestions":545},"Close",{"text":539,"link":540},"To search repositories and projects, login to",{"text":541,"config":542},"gitlab.com",{"href":201,"dataGaName":543,"dataGaLocation":544},"search login","search",{"text":546,"default":547},"Suggestions",[548,551,554,556,560,564],{"text":549,"config":550},"GitLab Duo Agent Platform",{"href":266,"dataGaName":549,"dataGaLocation":544},{"text":552,"config":553},"Code Suggestions (AI)",{"href":266,"dataGaName":552,"dataGaLocation":544},{"text":219,"config":555},{"href":221,"dataGaName":219,"dataGaLocation":544},{"text":557,"config":558},"GitLab on AWS",{"href":559,"dataGaName":557,"dataGaLocation":544},"/partners/technology-partners/aws/",{"text":561,"config":562},"GitLab on Google Cloud",{"href":563,"dataGaName":561,"dataGaLocation":544},"/partners/technology-partners/google-cloud-platform/",{"text":565,"config":566},"Why GitLab?",{"href":567,"dataGaName":565,"dataGaLocation":544},"/why-gitlab/",{"freeTrial":569,"mobileIcon":574,"desktopIcon":579,"secondaryButton":582},{"text":570,"config":571},"Start free trial",{"href":572,"dataGaName":192,"dataGaLocation":573},"https://gitlab.com/-/trials/new/","nav",{"altText":575,"config":576},"Gitlab Icon",{"src":577,"dataGaName":578,"dataGaLocation":573},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1758203874/jypbw1jx72aexsoohd7x.svg","gitlab icon",{"altText":575,"config":580},{"src":581,"dataGaName":578,"dataGaLocation":573},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1758203875/gs4c8p8opsgvflgkswz9.svg",{"text":583,"config":584},"Get Started",{"href":585,"dataGaName":586,"dataGaLocation":573},"https://gitlab.com/-/trial_registrations/new?glm_source=about.gitlab.com/get-started/","get started",{"freeTrial":588,"mobileIcon":592,"desktopIcon":594},{"text":589,"config":590},"Learn more about GitLab Duo",{"href":266,"dataGaName":591,"dataGaLocation":573},"gitlab duo",{"altText":575,"config":593},{"src":577,"dataGaName":578,"dataGaLocation":573},{"altText":575,"config":595},{"src":581,"dataGaName":578,"dataGaLocation":573},{"button":597,"mobileIcon":602,"desktopIcon":604},{"text":598,"config":599},"/switch",{"href":600,"dataGaName":601,"dataGaLocation":573},"#contact","switch",{"altText":575,"config":603},{"src":577,"dataGaName":578,"dataGaLocation":573},{"altText":575,"config":605},{"src":606,"dataGaName":578,"dataGaLocation":573},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1773335277/ohhpiuoxoldryzrnhfrh.png",{"freeTrial":608,"mobileIcon":613,"desktopIcon":615},{"text":609,"config":610},"Back to pricing",{"href":380,"dataGaName":611,"dataGaLocation":573,"icon":612},"back to pricing","GoBack",{"altText":575,"config":614},{"src":577,"dataGaName":578,"dataGaLocation":573},{"altText":575,"config":616},{"src":581,"dataGaName":578,"dataGaLocation":573},{"title":618,"button":619,"config":623},"GitLab Orbit is generally available. Increase agent accuracy and lower token cost",{"text":285,"config":620},{"href":287,"dataGaName":621,"dataGaLocation":622},"orbit-ga-banner","global-banner",{"layout":624,"disabled":29},"release",{"data":626},{"text":627,"config":628,"items":633,"minimal":859},"Git is a trademark of Software Freedom Conservancy and our use of 'GitLab' is under license",{"twitter":629,"facebook":630,"youtube":631,"linkedin":632},"https://twitter.com/gitlab","https://www.facebook.com/gitlab","https://www.youtube.com/channel/UCnMGQ8QHMAnVIsI3xJrihhg","https://www.linkedin.com/company/gitlab-com",[634,682,739,786,827],{"title":378,"links":635,"subMenu":651},[636,641,646],{"text":637,"config":638},"View plans",{"href":380,"dataGaName":639,"dataGaLocation":640},"view plans","footer",{"text":642,"config":643},"Why Premium?",{"href":644,"dataGaName":645,"dataGaLocation":640},"/pricing/premium/","why premium",{"text":647,"config":648},"Why Ultimate?",{"href":649,"dataGaName":650,"dataGaLocation":640},"/pricing/ultimate/","why ultimate",[652],{"title":653,"links":654},"Contact Us",[655,658,660,662,667,672,677],{"text":656,"config":657},"Contact sales",{"href":524,"dataGaName":197,"dataGaLocation":640},{"text":527,"config":659},{"href":529,"dataGaName":530,"dataGaLocation":640},{"text":532,"config":661},{"href":534,"dataGaName":535,"dataGaLocation":640},{"text":663,"config":664},"Status",{"href":665,"dataGaName":666,"dataGaLocation":640},"https://status.gitlab.com/","status",{"text":668,"config":669},"Terms of use",{"href":670,"dataGaName":671,"dataGaLocation":640},"/terms/","terms of use",{"text":673,"config":674},"Privacy statement",{"href":675,"dataGaName":676,"dataGaLocation":640},"/privacy/","privacy statement",{"text":678,"config":679},"Cookie preferences",{"dataGaName":680,"dataGaLocation":640,"id":681,"isOneTrustButton":176},"cookie preferences","ot-sdk-btn",{"title":205,"links":683,"subMenu":699},[684,687,689,691,693,695],{"text":685,"config":686},"Explore the platform",{"href":213,"dataGaName":207,"dataGaLocation":640},{"text":264,"config":688},{"href":266,"dataGaName":267,"dataGaLocation":640},{"text":219,"config":690},{"href":221,"dataGaName":222,"dataGaLocation":640},{"text":269,"config":692},{"href":271,"dataGaName":272,"dataGaLocation":640},{"text":251,"config":694},{"href":253,"dataGaName":254,"dataGaLocation":640},{"text":696,"config":697},"Why GitLab",{"href":567,"dataGaName":698,"dataGaLocation":640},"why gitlab",[700],{"title":13,"links":701},[702,706,711,715,719,724,729,734],{"text":219,"config":703},{"href":704,"dataGaName":705,"dataGaLocation":640},"/topics/ci-cd/","cicd",{"text":707,"config":708},"GitOps",{"href":709,"dataGaName":710,"dataGaLocation":640},"/topics/gitops/","gitops",{"text":216,"config":712},{"href":713,"dataGaName":714,"dataGaLocation":640},"/topics/devops/","devops",{"text":716,"config":717},"Version Control",{"href":19,"dataGaName":718,"dataGaLocation":640},"version control",{"text":720,"config":721},"DevSecOps",{"href":722,"dataGaName":723,"dataGaLocation":640},"/topics/devsecops/","devsecops",{"text":725,"config":726},"Cloud Native",{"href":727,"dataGaName":728,"dataGaLocation":640},"/topics/cloud-native/","cloud native",{"text":730,"config":731},"AI for Coding",{"href":732,"dataGaName":733,"dataGaLocation":640},"/topics/devops/ai-for-coding/","ai for coding",{"text":735,"config":736},"Agentic AI",{"href":737,"dataGaName":738,"dataGaLocation":640},"/topics/agentic-ai/","agentic ai",{"title":290,"links":740},[741,744,747,750,753,756,758,760,762,764,766,769,771,774,778,782],{"text":742,"config":743},"DevOps modernization",{"href":305,"dataGaName":306,"dataGaLocation":640},{"text":745,"config":746},"Security modernization",{"href":310,"dataGaName":311,"dataGaLocation":640},{"text":748,"config":749},"AI modernization",{"href":315,"dataGaName":316,"dataGaLocation":640},{"text":751,"config":752},"Financial services",{"href":341,"dataGaName":342,"dataGaLocation":640},{"text":754,"config":755},"Public sector",{"href":346,"dataGaName":347,"dataGaLocation":640},{"text":349,"config":757},{"href":351,"dataGaName":352,"dataGaLocation":640},{"text":354,"config":759},{"href":356,"dataGaName":357,"dataGaLocation":640},{"text":359,"config":761},{"href":361,"dataGaName":362,"dataGaLocation":640},{"text":364,"config":763},{"href":366,"dataGaName":367,"dataGaLocation":640},{"text":321,"config":765},{"href":323,"dataGaName":324,"dataGaLocation":640},{"text":767,"config":768},"Small business",{"href":328,"dataGaName":329,"dataGaLocation":640},{"text":331,"config":770},{"href":333,"dataGaName":334,"dataGaLocation":640},{"text":707,"config":772},{"href":773,"dataGaName":710,"dataGaLocation":640},"/solutions/gitops/",{"text":775,"config":776},"Software composition analysis",{"href":258,"dataGaName":777,"dataGaLocation":640},"software composition analysis",{"text":779,"config":780},"Value stream management",{"href":276,"dataGaName":781,"dataGaLocation":640},"value stream management",{"text":783,"config":784},"All solutions",{"href":297,"dataGaName":785,"dataGaLocation":640},"all solutions",{"title":383,"links":787},[788,793,798,800,802,804,806,808,810,812,814,816,818,820,823],{"text":789,"config":790},"Install",{"href":791,"dataGaName":792,"dataGaLocation":640},"/install/","install",{"text":794,"config":795},"Quick start guides",{"href":796,"dataGaName":797,"dataGaLocation":640},"/get-started/","quick setup checklists",{"text":395,"config":799},{"href":397,"dataGaName":398,"dataGaLocation":640},{"text":400,"config":801},{"href":402,"dataGaName":403,"dataGaLocation":640},{"text":405,"config":803},{"href":407,"dataGaName":408,"dataGaLocation":640},{"text":410,"config":805},{"href":412,"dataGaName":413,"dataGaLocation":640},{"text":415,"config":807},{"href":417,"dataGaName":418,"dataGaLocation":640},{"text":428,"config":809},{"href":430,"dataGaName":431,"dataGaLocation":640},{"text":433,"config":811},{"href":435,"dataGaName":436,"dataGaLocation":640},{"text":438,"config":813},{"href":440,"dataGaName":441,"dataGaLocation":640},{"text":443,"config":815},{"href":445,"dataGaName":446,"dataGaLocation":640},{"text":448,"config":817},{"href":162,"dataGaName":450,"dataGaLocation":640},{"text":510,"config":819},{"href":512,"dataGaName":513,"dataGaLocation":640},{"text":821,"config":822},"What's new",{"href":458,"dataGaName":459,"dataGaLocation":640},{"text":824,"config":825},"All resources",{"href":389,"dataGaName":826,"dataGaLocation":640},"all resources",{"title":461,"links":828},[829,831,833,835,837,839,841,843,845,849,854],{"text":469,"config":830},{"href":471,"dataGaName":463,"dataGaLocation":640},{"text":474,"config":832},{"href":476,"dataGaName":477,"dataGaLocation":640},{"text":480,"config":834},{"href":482,"dataGaName":483,"dataGaLocation":640},{"text":485,"config":836},{"href":487,"dataGaName":488,"dataGaLocation":640},{"text":490,"config":838},{"href":492,"dataGaName":493,"dataGaLocation":640},{"text":495,"config":840},{"href":497,"dataGaName":498,"dataGaLocation":640},{"text":500,"config":842},{"href":502,"dataGaName":503,"dataGaLocation":640},{"text":505,"config":844},{"href":507,"dataGaName":508,"dataGaLocation":640},{"text":846,"config":847},"Sustainability",{"href":848,"dataGaName":846,"dataGaLocation":640},"/sustainability/",{"text":850,"config":851},"Diversity, inclusion and belonging (DIB)",{"href":852,"dataGaName":853,"dataGaLocation":640},"/diversity-inclusion-belonging/","Diversity, inclusion and belonging",{"text":855,"config":856},"Modern Slavery Transparency Statement",{"href":857,"dataGaName":858,"dataGaLocation":640},"https://handbook.gitlab.com/handbook/legal/modern-slavery-act-transparency-statement/","modern slavery transparency statement",{"items":860},[861,864,867],{"text":862,"config":863},"Terms",{"href":670,"dataGaName":671,"dataGaLocation":640},{"text":865,"config":866},"Cookies",{"dataGaName":680,"dataGaLocation":640,"id":681,"isOneTrustButton":176},{"text":868,"config":869},"Privacy",{"href":675,"dataGaName":676,"dataGaLocation":640},{"header":871,"blurb":872,"button":873,"secondaryButton":878},"Start building faster today","See what your team can do with the intelligent orchestration platform for DevSecOps.\n",{"text":874,"config":875},"Get your free trial",{"href":876,"dataGaName":192,"dataGaLocation":877},"https://gitlab.com/-/trial_registrations/new?glm_content=default-saas-trial&glm_source=about.gitlab.com/","feature",{"text":656,"config":879},{"href":524,"dataGaName":197,"dataGaLocation":877},1794911794329]