GIT Workshop 2014: Unterschied zwischen den Versionen
aus Metalab Wiki, dem offenen Zentrum für meta-disziplinäre Magier und technisch-kreative Enthusiasten.
Zur Navigation springenZur Suche springen
KKeine Bearbeitungszusammenfassung |
K (→Task 1) |
||
| Zeile 47: | Zeile 47: | ||
== Task 1 == | == Task 1 == | ||
A quick | A quick and easy task to get you started: | ||
# Clone or fork the [https://github.com/metachris/metalab-git-workshop workshop | |||
# Clone or fork the [https://github.com/metachris/metalab-git-workshop workshop repository] and make a change (change literally anything). See also the [https://help.github.com/categories/54/articles Github Bootcamp] | |||
# Send me a [http://stackoverflow.com/questions/2082296/how-do-patches-work-in-git patch] or [https://help.github.com/articles/using-pull-requests pull-request], either on Github or to chris [at] linuxuser.at | # Send me a [http://stackoverflow.com/questions/2082296/how-do-patches-work-in-git patch] or [https://help.github.com/articles/using-pull-requests pull-request], either on Github or to chris [at] linuxuser.at | ||
+1. Thanks for your contribution to an open source project. | +1. Thanks for your contribution to an open source project. | ||
= When / Where = | = When / Where = | ||
Version vom 12. Mai 2014, 22:06 Uhr
| GIT Workshop 2014 | |
| |
| 27.05.2014, 19:00 | |
| metachris | |
| Workshop | |
| 0 | |
| planning | |
| so much stuff is happening! it will be a great party! everbody come! | |
| Zuletzt aktualisiert: | 12.05.2014 |
Hands-On GIT Workshop in two or more parts which will make your life easy and may save your ass / day off!
https://github.com/metachris/metalab-git-workshop
General Topics
- Commiting, Diffing, Reverting, Tags
- Branches, Merging and Conflicts
- Remotes, Github, Forking, Pull-Requests
- Working together within a repository and across repos
- Contributing to open source projects
- Workflows for teams and dev->testing->production environments
- Issue tracking
- Stashing, Sqashing, Rebasing, Submodules
- Code reviews with GIT, Jenkins CI
- Automatic code-style checks at
git commit - < YOUR TOPIC IDEA >
It's a command-line oriented workshop where all hands get dirty. We celebrate failure and are going to have fun! :)
Every skill level from is welcome! We'll start on Tue, 27.5.2014 (19:00) and see how and where we progress; primarily based on your interests, experiences and current projects/needs.
Prerequisites
- You are somewhat familiar with the terminal/command line
- You have
git-coreinstalled (can rungitin the command line) - You added yourself to the participants (further down)
- You have an account at Github
- You tried task 1
Task 1
A quick and easy task to get you started:
- Clone or fork the workshop repository and make a change (change literally anything). See also the Github Bootcamp
- Send me a patch or pull-request, either on Github or to chris [at] linuxuser.at
+1. Thanks for your contribution to an open source project.
When / Where
- Tue, 27.5.2014, 19:00, Hauptraum
Participants
Please add yourself to the list of participants.
Various
# Possibly useful Git aliases for your ~/.bashrc or ~/.bash_profile alias g='git' alias gs='git status | more' alias ga='git add ' alias gb='git branch ' alias gc='git commit' alias gcnv="git commit --no-verify" alias gd='git diff' alias go='git checkout ' alias gl='git log' alias gh='git log --pretty=format:"%h %ad | %s%d [%an]" --graph --date=short'
- Git-Flow: http://nvie.com/posts/a-successful-git-branching-model (I like the general idea but personally don't use the git-flow tools)
- Semantic Versioning: http://semver.org
