By Use Case
By Organization Type
Meet Our Partners
Discover all-in-one software delivery.
See repositories in action with GitLab projects.
Install one pacakge, run a complete solution.
See why we're the best in DevOps
Automate everything, accelerate deployment.
Build the future with a shared history.
Adopt DevOps with a single commit.
Integrate security, deliver faster continuously.
Keep your methodology, gain functionality.
Visualize what works and optimize the rest.
Simplify IT with DevOps-style automation.
Get a DevOps platform that grows with you.
Adopt one platform for endless possibilities.
Explore our quick-start checklist.
Get cross-functional software delivery insights.
Access step-by-step tutorials and guides.
Watch videos and self-driven demos.
Read up on releases, contributions, and more.
Adopt DevOps faster with our support services.
Download knowledge, expand to production.
Discover how we work better together – wherever.
Access contributor resources and startup grants.
Find meetups, webinars, conferences, and more.
See DevSecOps through the eyes of practitioners
Check out our technology and channel partners.
Learn why top companies trust GitLab for DevOps.
See our cloud partners and other integrators.
Join our DevOps partner ecosystem.
Find resellers, solution providers, and more.
Grow your business alongside our DevOps experts.
See options for projects and teams of every size.
Find out how, where, and when we offer support.
Explore support documents and instructions.
Users occasionally write in to say that there is a commit from the incorrect or an unknown user or email.
It is part of Support's responsibility to determine whether this is due to a misconfiguration (which is common) or a true security incident.
For more information on using Kibana in general, please see 500 errors workflow.
To find the user who made the commit:
If logs are unavailable in Kibana (older than 7 days), try searching the project's activity page for the SHA. If that doesn't work, post in Slack #security for assistance.
Based on the search results, check to see if the user is authorized to have access to the project.
If yes, then respond to customer clarifying which user made the commit and for the user to double check their gitconfig name and email address.
If not, then open a a secops issue for further investigation.