Development using git: Difference between revisions

From Alpine Linux
No edit summary
 
(33 intermediate revisions by 12 users not shown)
Line 1: Line 1:
This document describes how to use [http://git-scm.com git] for Alpine Linux development and related projects.
{{Move|Git|All git development articles should be consolidated}}
 
This document describes how to use [https://git-scm.com git] for Alpine Linux development and related projects. If you just want to browse the Alpine git repositories, please visit [https://git.alpinelinux.org/aports git.alpinelinux.org].


== Basic Git usage ==
== Basic Git usage ==
Line 6: Line 8:


{{Tip| If you want to use git with colored output use:
{{Tip| If you want to use git with colored output use:
  {{Cmd|git config --global color.ui true}}
  {{Cmd|git config --global color.ui true
git config --global core.pager more}}
}}
}}


{{:Development_using_git:Email}}
{{Tip| If you want to use git with proxy server:
{{Cmd|git config --global http.proxy <nowiki>http://proxy_ip:proxy_port</nowiki>}}
}}
 
== Cloning a repository via Git ==
 
There are two ways to work with the Alpine git repository...
 
* ...without write access.
* ...with write access.
 
[https://git.alpinelinux.org/aports git.alpinelinux.org] shows all available Alpine git repositories.


== Cloning the repository via Git ==
=== Without write access ===
 
If you want to clone the Alpine aports repository, switch to the directory you want to have the ''aports/'' directory in and launch git.
   
   
{{Cmd|git clone git://git.alpinelinux.org/aports.git}}
{{Cmd|git clone <nowiki>git://git.alpinelinux.org/aports.git</nowiki>}}
The full aports repository is now copied to your ''aports/.git'' dir and the latest commit is checked out in ''aports/''. Most operations you do from here will happen on your local copy and will not affect git.alpinelinux.org.
 
{{Tip| If you are using proxy server:
{{Cmd|git clone https://git.alpinelinux.org/aports}}
}}


If you want only the last 3 revisions:
If you want only the last 3 revisions:
{{Cmd|git clone git://git.alpinelinux.org/aports.git --depth 3}}
{{Cmd|git log}}
to see the full log of the trunk.


You can also browse the git repository via [http://git.alpinelinux.org/cgit/aports cgit].
{{Cmd|git clone <nowiki>git://git.alpinelinux.org/aports.git</nowiki> --depth 3}}
== General GIT Workflow ==
# Make your file edits in your local checkout of the local copy of repository.
# ''git commit''      the changes in your local repository
# ''git pull --rebase''  to bring the rest of your local repository up to date
# ''git log origin..master'' to check what you are going to commit
# ''git push''    to move your changes up to the master. This requires you have an ssh login and have cloned via ssh://git.alpinelinux.org and not via git://git.alpinelinux.org. (see [[Development using git with write access]])


{{Cmd|git stash}}    if you want to "hide" your changes.  Do this if you think there may be other commits against the same things you are working on and want to refresh your local checkout (using a git pull --rebase) from the master. Use ''git stash apply'' to get your stash back.  
Use the command below to see the full log of the trunk.  


{{Cmd|git checkout -f master}} if you think your tree is pretty hopeless, need a kill-and-fill to bring the master into your local repository. You will lose local changes.
{{Cmd|git log}}
 
== List the local branch ==
You can now list your local branch by doing
{{Cmd|git branch}}
which should ouput
* master


== List your local non committed changes ==
=== Submitting work without write access ===
{{Cmd|git status}}


== Commit ==
You can still [https://wiki.alpinelinux.org/wiki/Creating_patches submit a patch] without write access to the Alpine repository. For this you need to create an account on Alpine's GitLab, fork the desired repository (the fork resides on the server), clone the fork on your computer, make your changes into a separate branch, push the squashed branch to the fork (as branch; do not merge/rebase it into the master!) and create a merge request for that branch through the GitLab Web GUI.
Now you can start to work on your tree. As soon as you feel you have reached a step in developement where you can commit your work '''locally''', use
{{Cmd|git commit -a}}
or
{{Cmd|git commit <specific files>}}
or
{{Cmd|git add <specific files>
git commit}}


If you wish to give credit to someone else's work (e.g. you are applying a third party patch):
=== With write access ===
{{Cmd|git commit <specific files> --author "Name Surname <user@example.com>}}


The format of the commit message should be:
If you have write access to the Alpine repository, the URL needs to be adjusted for cloning a repository
One-line descrption thats less than 72 chars long
''<second line empty>''
Optional longer description with explanation why changes were made. Links to relevant issues
in bugtracker can be done with:
  ref #<issuenumber>
It is also possible to resolve issues with:
  fixes #<issuenumber>


{{Cmd|git clone git@git.alpinelinux.org:aports}}


Think of first line as the subject in an email and the third line and on as the body of the email, describing what the commit does. You dont need the long description but the first line, the short description should be there as it will be showed in the commit log.
Alternatively you can set the remote url of an exisiting git clone:
{{Cmd|git remote set-url origin git@git.alpinelinux.org:aports}}


== List your commits ==
== General GIT Workflow ==
{{Cmd|git log}}
# Make your file edits in your local checkout of the local copy of repository.
# Commit the changes in your local repository: {{Cmd|git commit}}
# Bring the rest of your local repository up to date: {{Cmd|git pull --rebase}}
# Check what you are going to push: {{Cmd|git log origin..master}}
# Move your changes up to the master if you have write access {{Cmd|git push}} or [[Creating_patches|create a patch]] if not.


== Other related articles ==


== Keeping your local working branch in sync ==
* [[Development_using_git:Basic_usage| Basic usage]]
Pull the changes from upstream (git.alpinelinux.org)
* [[Package Maintainers]]
{{Cmd|git pull --rebase}}
* [[Creating patches]]
* [[Development_using_git:Developer_repositories|Developer repositories]]
* [[Development_using_git:Cgit| Using Cgit]]
* [[Development using git:Quality assurance]]
* [[Gitolite]]


= Documentation about git =
== Further reading ==
Some other useful documents
{{:Development_using_git:Documentation}}
*[http://www.kernel.org/pub/software/scm/git/docs/ Git Tutorial]
*[http://git.or.cz/course/svn.html Git - SVN Crash Course] (quickstart if you know svn)
*[http://cworth.org/hgbook-git/tour/ A tour of git: the basics] '''Recommended'''
*[http://book.git-scm.com/ The Git Community Book]
* [http://wiki.sourcemage.org/Git_Guide Very good Git guide]


[[Category:Development]]
[[Category:Development]]
[[Category:Git]]

Latest revision as of 06:47, 23 August 2023

This page is proposed for moving ...

It should be renamed to Git. All git development articles should be consolidated (Discuss)

This document describes how to use git for Alpine Linux development and related projects. If you just want to browse the Alpine git repositories, please visit git.alpinelinux.org.

Basic Git usage

Configure your global git config

First you need to tell your name and email to git. This name and email will show up in all your commits.

git config --global user.name "Your Name Comes Here" git config --global user.email you@yourdomain.example.com

Using git config without --global let you configure other details for a specific git repository.

Tip: If you want to use git with colored output use:

git config --global color.ui true git config --global core.pager more

Tip: If you want to use git with proxy server:

git config --global http.proxy http://proxy_ip:proxy_port

Cloning a repository via Git

There are two ways to work with the Alpine git repository...

  • ...without write access.
  • ...with write access.

git.alpinelinux.org shows all available Alpine git repositories.

Without write access

If you want to clone the Alpine aports repository, switch to the directory you want to have the aports/ directory in and launch git.

git clone git://git.alpinelinux.org/aports.git

Tip: If you are using proxy server:

git clone https://git.alpinelinux.org/aports

If you want only the last 3 revisions:

git clone git://git.alpinelinux.org/aports.git --depth 3

Use the command below to see the full log of the trunk.

git log

Submitting work without write access

You can still submit a patch without write access to the Alpine repository. For this you need to create an account on Alpine's GitLab, fork the desired repository (the fork resides on the server), clone the fork on your computer, make your changes into a separate branch, push the squashed branch to the fork (as branch; do not merge/rebase it into the master!) and create a merge request for that branch through the GitLab Web GUI.

With write access

If you have write access to the Alpine repository, the URL needs to be adjusted for cloning a repository

git clone git@git.alpinelinux.org:aports

Alternatively you can set the remote url of an exisiting git clone:

git remote set-url origin git@git.alpinelinux.org:aports

General GIT Workflow

  1. Make your file edits in your local checkout of the local copy of repository.
  2. Commit the changes in your local repository:

    git commit

  3. Bring the rest of your local repository up to date:

    git pull --rebase

  4. Check what you are going to push:

    git log origin..master

  5. Move your changes up to the master if you have write access

    git push

    or create a patch if not.

Other related articles

Further reading

Retrieved from "https://wiki.alpinelinux.org/w/index.php?title=Development_using_git&oldid=24411"