@article{choudhuryGitLabWorkWhere2020,
	title = {{GitLab}: work where you want, when you want},
	volume = {9},
	issn = {2245-408X},
	shorttitle = {{GitLab}},
	url = {https://doi.org/10.1186/s41469-020-00087-8},
	doi = {10.1186/s41469-020-00087-8},
	abstract = {GitLab is a software company that works “all remote” at the scale of more than 1000 employees located in more than 60 countries. GitLab has no physical office and its employees can work from anywhere they choose. Any step of the organizational life of a GitLab employee (e.g., hiring, onboarding and firing) is performed remotely, except for a yearly companywide gathering. GitLab strongly relies on asynchronous coordination, allowing employees to work anytime they want. After highlighting some of the main practices implemented by GitLab to effectively work all remotely and asynchronously, I asked renowned organizational scientists their thoughts on this interesting case and to question the generalizability of the all remote asynchronous model. Understanding whether and under what conditions this model can succeed can be of guidance for organizational designers that are now considering different remote models in response of the COVID-19 shock and its aftermath.},
	language = {en},
	number = {1},
	urldate = {2026-04-15},
	journal = {Journal of Organization Design},
	author = {Choudhury, Prithwiraj and Crowston, Kevin and Dahlander, Linus and Minervini, Marco S. and Raghuram, Sumita},
	month = nov,
	year = {2020},
	keywords = {All remote, COVID-19, New forms of organizing, Organizational design, Remote work, Virtual organizations},
	pages = {23},
	file = {Full Text PDF:C\:\\Users\\Roman\\Zotero\\storage\\IT677T3E\\Choudhury et al. - 2020 - GitLab work where you want, when you want.pdf:application/pdf},
}

@article{arefeen_continuous_2019,
	title = {Continuous {Integration} {Using} {Gitlab}},
	volume = {3},
	issn = {2561-5637},
	url = {https://www.urncst.com/index.php/urncst/article/view/152},
	doi = {10.26685/urncst.152},
	abstract = {The method of Continuous Integration (CI) enables developers to use fast-paced development environments, such as Agile, without the quality of code being compromised. The use of stable repositories on which developers frequently make small changes, running tests with each modification, results in code that is highly tested and readily deployable. GitLab, like other tools of its kind, offers CI features along with code versioning, and several team organizational features that correctly map with Agile artifacts. Before discussing GitLab, this report contains a literature review explaining existing CI practices, and it identifies fundamental aspects that are necessary to achieving the industry standards of CI. This report also evaluates GitLab’s effectiveness in maintaining CI standards using an available open-source project (OpenMCT), while also offering insight on the implications of the gathered findings. The paper concludes with possible directions of future inquiry, and also provides guidance on how one might expand on the work initiated by the team.},
	language = {en},
	urldate = {2026-04-15},
	journal = {Undergraduate Research in Natural and Clinical Science and Technology Journal},
	author = {Arefeen, Mohammed Shamsul and Schiller, Michael},
	month = sep,
	year = {2019},
	keywords = {agile, continuous integration, GitLab, software testing},
	pages = {1--6},
}

@misc{gitlab_gitlab_nodate,
	title = {{GitLab} {Docs}},
	url = {https://docs.gitlab.com/},
	urldate = {2026-04-16},
	author = {{Gitlab}},
}

@misc{degeler_gitlab_2014,
	title = {{GitLab} is building a business with 0.1\% of paying customers},
	url = {https://thenextweb.com/news/github-rival-gitlab-building-business-just-0-1-paying-customers},
	abstract = {Long-distance relationships are never easy, but it seems to be less so for the relationships between co-founders of tech companies. See GitLab, for example.},
	language = {en},
	urldate = {2026-04-16},
	author = {Degeler, Andrii},
	month = jun,
	year = {2014},
	annote = {Section: Insider},
}

@misc{gitlab_about,
	title = {About {Gitlab}},
	url = {https://about.gitlab.com/},
	abstract = {Your intelligent orchestration platform for DevSecOps},
	language = {en-US},
	urldate = {2026-04-17},
	journal = {about.gitlab.com},
	author = {Gitlab},
	file = {Snapshot:C\:\\Users\\Roman\\Zotero\\storage\\T886BE4A\\about.gitlab.com.html:text/html},
}

@misc{GitLabcomDatabaseIncident,
	title = {{GitLab}.com database incident},
	url = {https://about.gitlab.com/blog/gitlab-dot-com-database-incident/},
	abstract = {Yesterday we had a serious incident with one of our databases. We lost six hours of database data (issues, merge requests, users, comments, snippets, etc.) for GitLab.com.},
	language = {en-US},
	urldate = {2026-04-17},
	journal = {about.gitlab.com},
	file = {Snapshot:C\:\\Users\\Roman\\Zotero\\storage\\LBYJ7RZX\\gitlab-dot-com-database-incident.html:text/html},
}

@misc{onlineVersionsverwaltungGitLabRudert2022,
	title = {Versionsverwaltung: {GitLab} rudert beim {Löschen} inaktiver {Repositories} zurück},
	shorttitle = {Versionsverwaltung},
	url = {https://www.heise.de/news/Versionsverwaltung-GitLab-rudert-beim-Loeschen-inaktiver-Repositories-zurueck-7203006.html},
	abstract = {Die Pläne, brach liegende Repositories komplett zu löschen, sind laut einem Tweet von GitLab vorerst auf Eis gelegt. Stattdessen sollen sie archiviert werden.},
	language = {de},
	urldate = {2026-04-17},
	journal = {Developer},
	author = {online, heise},
	month = aug,
	year = {2022},
	file = {Snapshot:C\:\\Users\\Roman\\Zotero\\storage\\3N8Y75DY\\Versionsverwaltung-GitLab-rudert-beim-Loeschen-inaktiver-Repositories-zurueck-7203006.html:text/html},
}