Fix typos (GitHub, GitLab)
This commit is contained in:
@@ -1,5 +1,5 @@
|
||||
---
|
||||
title: "Gitlab CI"
|
||||
title: "GitLab CI"
|
||||
ring: assess
|
||||
quadrant: tools
|
||||
---
|
||||
|
||||
@@ -1,11 +1,11 @@
|
||||
---
|
||||
title: "Gitlab"
|
||||
title: "GitLab"
|
||||
ring: trial
|
||||
quadrant: tools
|
||||
---
|
||||
|
||||
[Gitlab](https://about.gitlab.com/) provides nearly the same feature set as [Github](https://github.com/), but at a lower price. It also provides the possibility of hosting internally, which is essential for us.
|
||||
[GitLab](https://about.gitlab.com/) provides nearly the same feature set as [GitHub](https://github.com/), but at a lower price. It also provides the possibility of hosting internally, which is essential for us.
|
||||
|
||||
We are migrating more and more repositories from [gitolite](http://gitolite.com/gitolite/index.html), even from SVN to gitlab, as it provides a more stable and user-friendly interface.
|
||||
We are migrating more and more repositories from [gitolite](http://gitolite.com/gitolite/index.html), even from SVN to GitLab, as it provides a more stable and user-friendly interface.
|
||||
|
||||
Gitlab also makes user/permission handling easier than our old gitolite. We don't need the IT team every time a new repository needs to be set up.
|
||||
GitLab also makes user/permission handling easier than our old gitolite. We don't need the IT team every time a new repository needs to be set up.
|
||||
|
||||
@@ -7,4 +7,4 @@ quadrant: methods-and-patterns
|
||||
|
||||
We moved this pattern to **adopt**, because it is used by nearly every team and project now and is an important part of our automation.
|
||||
|
||||
For Jenkins, we often use a mix of Job DSL and Jenkins Pipelines and recently also used Gitlab Pipelines.
|
||||
For Jenkins, we often use a mix of Job DSL and Jenkins Pipelines and recently also used GitLab Pipelines.
|
||||
|
||||
Reference in New Issue
Block a user