gitlab | 易学教程

Automatically merge one branch into another basis on some conditions using hook?

阅读更多关于 Automatically merge one branch into another basis on some conditions using hook?

问题 I have two branches in my github repository - master and dev branch. I have a requirement where I need to merge master branch into dev branch under below conditions: Once a PR is merged into master branch directly then I need to merge master branch back to dev branch automatically. Whenever someone adds a commit into master branch directly then I need to merge master branch back to dev branch automatically. Is this possible to do by any chance? I believe we can make this work with git Hooks

Automatically merge one branch into another basis on some conditions using hook?

阅读更多关于 Automatically merge one branch into another basis on some conditions using hook?

In GitLab's CI/CD system how do I prevent a job from running if it's in my fork and only allow it to run if its a merge to the main repo?

阅读更多关于 In GitLab's CI/CD system how do I prevent a job from running if it's in my fork and only allow it to run if its a merge to the main repo?

问题 I have a job in my gitlab-ci.yml like build and push: stage: push only: - master script: - gcloud docker -- push $IMAGE_TAG The idea being that it should only run if the branch is master, but I also only want it to run if the repo is app/ and not dave/ The docs say The repository path can be used to have jobs executed only for the parent repository and not forks: job: only: - branches@gitlab-org/gitlab-ce but I can't get this to work. If our gitlab server is gitlab.myco.io and the app is app

Gitlab-CI (under gitlab.com) “system failure” starting container process

阅读更多关于 Gitlab-CI (under gitlab.com) “system failure” starting container process

问题 This is my 1st try to set up a basic CI workflow on gitlab.com . The concerned project is a basic static website, and I wanted to run some npm install and gulp build directly on gitlab. I created a .gitlab-ci.yml file, which is recognized and launched. But firsts implementations failed, so I came back to the more basic CI script ever, as follows: image: debian:jessie stages: - build build: stage: build script: echo "Building the app" Even in this case I encounter the same error: ERROR: Job

解决gitLab上新建分支，idea中找不到对应分支问题

阅读更多关于解决gitLab上新建分支，idea中找不到对应分支问题

解决gitLab上新建分支，idea中找不到对应分支问题参考文章：（1）解决gitLab上新建分支，idea中找不到对应分支问题（2）https://www.cnblogs.com/meituan/p/11050858.html 备忘一下。来源： oschina 链接： https://my.oschina.net/u/4438370/blog/4776181

孙叫兽进阶之路之Gitlab的使用（图文教程）

阅读更多关于孙叫兽进阶之路之Gitlab的使用（图文教程）

简介： GitLab是一个利用 Ruby on Rails 开发的开源应用程序，实现一个自托管的 Git 项目仓库，可通过Web界面进行访问公开的或者私人项目。它拥有与 Github 类似的功能，能够浏览源代码，管理缺陷和注释。可以管理团队对仓库的访问，它非常易于浏览提交过的版本并提供一个文件历史库。它还提供一个代码片段收集功能可以轻松实现代码复用，便于日后有需要的时候进行查找。 GitLab 5.0以前版本要求服务器端采用 Gitolite 搭建，5.0版本以后不再使用 Gitolite ，采用自己开发的 gitlab-shell 来实现。如果你觉得安装麻烦可以使用 GitLab Installers 一键安装程序。 GitLab 是一个用于仓库管理系统的开源项目，使用 Git 作为代码管理工具，并在此基础上搭建起来的web服务，安装方法如下。这样就完成了图形化界面小乌龟操作gitlab的基本配置。来源： oschina 链接： https://my.oschina.net/u/4272693/blog/4776137

Gitlab code review batch comments?

阅读更多关于 Gitlab code review batch comments?

问题 Is it possible to get batch comments in Gitlab when doing a code review? Similar to Phabricator, where you only get one email when the reviewer makes multiple comments on your code? We are trying to use Gitlab at work, and feel kind of spammed by the individual emails per comment. Thanks 回答1: This is now available as per this news 回答2: There is an open feature proposal for this here. 来源： https://stackoverflow.com/questions/25104473/gitlab-code-review-batch-comments

Gitlab code review batch comments?

阅读更多关于 Gitlab code review batch comments?

git fsck: duplicateEntries: contains duplicate file entries - cannot push to gitlab

阅读更多关于 git fsck: duplicateEntries: contains duplicate file entries - cannot push to gitlab

问题 We have a big git repository, which I want to push to a self-hosted gitlab instance. The problem is that the gitlab remote does not let me push my repo: git push --mirror https://mygitlab/xy/myrepo.git This will give me this error: Enumerating objects: 1383567, done. Counting objects: 100% (1383567/1383567), done. Delta compression using up to 8 threads Compressing objects: 100% (207614/207614), done. remote: error: object c05ac7f76dcd3e8fb3b7faf7aab9b7a855647867: duplicateEntries: contains

cr5

阅读更多关于 cr5

1、首先是团队知识共享的角度一个开发团队中，水平有高有低，每个人侧重的领域也有不同，怎么让高水平的帮助新人成长？怎么让大家都对自己侧重领域之外的知识保持了解？怎么能有人离职后其他人能快速接手？这些都是团队管理者关心的问题。而代码审查，就是一个很好的知识共享的方式。通过代码审查，高手可以直接指出新手代码中的问题，新手可以马上从高手的反馈中学习到好的实践，得到更快的成长。通过代码审查，前端也可以去学习后端的代码，做功能模块A的可以去了解功能模块B的，可能有些高手觉得给新手代码审查浪费时间，自己也没收获。其实不然，新人成长了，就可以更多的帮高手分担繁重的任务；代码审查中花时间，就少一些帮新人填坑擦屁股的时间；良好的沟通能力、发现问题的能力、帮助其他人成长，都是技术转管理或技术上更上一层楼必不可少的能力，而通过代码审查可以有效的去练习这些方面的能力。 2、代码质量的角度现实中的项目总是人手缺进度紧，所以被压缩的往往就是自动化测试和代码审查，结果影响代码质量，欠下技术债务，最后还是要加倍偿还。也有人寄希望于开发后的人工测试，然而对于代码质量来说，很多问题通过测试是测试不出来的，只能通过代码审查，比如说代码的可读性可维护性，比如代码的结构，比如一些特定条件才触发的死循环、逻辑算法错误，还有一些安全上的漏洞也更容易通过代码审查发现和预防。