Difference between revisions of "Git / Gitlab"

From LinuxMCE
Jump to: navigation, search
(With no write access)
(Useful links)
Line 45: Line 45:
 
# Merge your changes into Master
 
# Merge your changes into Master
 
# Push the verified changes to master
 
# Push the verified changes to master
 +
 +
== GitLab IRC ==
 +
To enable IRC notifications for your project add a Web Hooks (Settings -> Web hook) with the URL http://localhost:4567/commit
 +
Somehow GitLab seems to ignore "Trigger". When only checked "Push events" it's still triggered for Comments, Issue events etc.
 +
 +
Because of that fact i extended the config.yml of giltab-irc (/home/git/gitlab-irc/config/config.yml) to have at least the option to configure notifications globally.
 +
 +
Following options for notifications:
 +
<pre>
 +
msg:
 +
  push: true
 +
  tag_push: false
 +
  issue: true
 +
  note: false
 +
</pre>
 +
 +
To start gitlab-irc open a screen and run:
 +
<pre>
 +
cd /home/git/gitlab-irc && foreman start
 +
</pre>
  
 
== Useful links ==
 
== Useful links ==

Revision as of 23:05, 11 January 2016

GitLab / GIT

GitLab is the web interface of choice for managing GIT repositories.

A list of features: https://about.gitlab.com/features/

Additional Info:

  • GitLab URL: https://git.linuxmce.org/
  • Repository URL: https://git.linuxmc.org/< username / group name >/< project name >.git

Get access to GitLab

Go to IRC #linuxmce-devel and ask for a Account.

To create an account we need following information:

  1. Name
  2. Username
  3. E-Mail

As soon as your account was created you'll receive an E-Mail containing a link to set your password. Klick on that link and set your password, then you are ready to login.

Workflow

We have no fine grained workflow at the moment and no continous integration.

With no write access

Even if you have write access you can use this method.

  1. Fork a repository
  2. Do your stuff, implement features, fix bugs etc.
  3. Make "Pull Request" for your changes
  4. "Pull Request" will be verified and merged by a LinuxMCE Dev, please be patient

With write access

Master is always deployable, so we must not work on Master at any time!
Master is only used for merge in working stuff.

  1. Clone a repository
  2. Branch of from Master
  3. Do your stuff, implement features, fix bugs etc.
  4. Commit/Push your branch - on bigger changes i would recommend doing a test build using this branch
  5. Merge your changes into Master
  6. Push the verified changes to master

GitLab IRC

To enable IRC notifications for your project add a Web Hooks (Settings -> Web hook) with the URL http://localhost:4567/commit Somehow GitLab seems to ignore "Trigger". When only checked "Push events" it's still triggered for Comments, Issue events etc.

Because of that fact i extended the config.yml of giltab-irc (/home/git/gitlab-irc/config/config.yml) to have at least the option to configure notifications globally.

Following options for notifications:

msg:
  push: true
  tag_push: false
  issue: true
  note: false

To start gitlab-irc open a screen and run:

cd /home/git/gitlab-irc && foreman start

Useful links