-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Intro to version control, git and GitHub (/GitLab) #58
Comments
Looks like most people are familiar with git and GitHub (#22), so this may not be worth doing. |
I would not consider myself qualified. I am interested in attending to learn more though! |
Paging @tiborsimko! |
I think a pedestrian guide to CI at CERN might be interesting. I.e., not just version control. |
I'm moving to CERN next week, so I'll be able to do these kinds of sessions in the future :) If everyone is already familiar with git, I could do some semi-advanced things like @adavidzh: I've played around with using Gitlab runners with the CERN Gitlab instance, so I'd be able to show how to set up an OpenStack instance for Gitlab CI. (But not much more beyond that). |
@ibab: Up for this tomorrow? :D |
Nope, can't make it this week. :( On Thu, Oct 20, 2016, 13:15 RaoOfPhysics [email protected] wrote:
|
@RaoOfPhysics basically I'm out every Friday... (that's the day that I'm at uni). @ibab Not sure I've anything more to add, but I've done some playing around with Docker + Gitlab-CI + CERN Gitlab-CI auto building of Docker images + ... (before docker.cern.ch was deprecated) |
Sorry @RaoOfPhysics I didn't notice your ping before... busy times. Anyway I think @ibab volunteered to take care of this intro now. Speaking of somewhat more advaned usage of git, it may be good to cover also efficient integration with code editors (e.g. Emacs Magit) and how it can improve interactive rebasing, blaming, bisecting, etc. Touching various merging strategies and Git shortcuts and aliases are also useful, e.g. try this one for nicely formatted commit history: $ grep ka ~/.gitconfig
ka = log --graph --decorate --pretty=format:'%C(blue)%d%Creset %C(yellow)%h%Creset %s, %C(bold green)%an%Creset, %C(green)%cd%Creset' --date=relative --all so this one for "local branch information": $ grep lbi ~/.gitconfig
lbi = !"git for-each-ref --format='%(committerdate:short) %(refname)' --sort=committerdate refs/heads/*$1*" Speaking of GitHub CLI tools, I quite like ghi for working with issues, labels and friends. (...just some random musings in between two things....) |
@tiborsimko: I believe @ibab is off to greener pastures soon! Not sure when, though. If he's not around, would you be up for this? We'll have to do it in the new year, I presume, and not on a Friday (for @stklik). |
Anyone want to teach this? @ibab, @tpmccauley, @jacquerie?
The text was updated successfully, but these errors were encountered: