Difference between revisions of "Git / Gitlab"
From LinuxMCE
Line 4: | Line 4: | ||
A list of features: https://about.gitlab.com/features/ | A list of features: https://about.gitlab.com/features/ | ||
+ | |||
+ | Additional Info: | ||
+ | |||
+ | * GitLab URL: https://git.linuxmce.org/ | ||
+ | * Repository URL: <nowiki>https://git.linuxmc.org/< username / group name >/< project name >.git</nowiki> | ||
== Get access to GitLab == | == Get access to GitLab == |
Revision as of 08:39, 6 January 2016
Contents
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:
- Name
- Username
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.
- Fork a repository
- Do your stuff, implement features, fix bugs etc.
- Make "Pull Request" fo your changes
- "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!
- Clone a repository
- Branch of from Master
- Do your stuff, implement features, fix bugs etc.
- Commit/Push your branch - on bigger changes i would recommend doing a test build using this branch
- Merge your changes into Master
- Push the verified changes to master
Useful links
- GIT clients: http://git-scm.com/downloads/guis
- GIT Docs: http://git-scm.com/docs
- Cheatsheet / Commands:
- Merge vs. Rebase: https://www.atlassian.com/git/tutorials/merging-vs-rebasing/conceptual-overview