...to checkout the branch groups, you can simply say this in recent versions of Git: git fetch origin git checkout groups This will automatically track origin/groups from a local branch...
In older Git versions you need to say this: git fetch origin git checkout --track origin/groups
Make a new commit now, with a message like "fix". Do a git rebase -i OLD_COMMIT~ In the editor window that opened, move the "fix" commit directly...
...fixup". Save the file. If there are conflicts, solve them, add them, and do git rebase --continue
...stalled like this: [err :: host.name.tld] Username: It turned out that I this originated from GitHub. We had a gem in...
...our Gemfile that explicitly pointed to a GitHub URL like that: gem 'foogem', :git => 'https://github.com/blubb/foogem.git' The URL was returning a 404 which caused the problems. You have to...
Sometimes, due to git or other "accidents", important files get deleted or overwritten. At a state when even Ctrl+Z doesn't work anymore, you maybe can rescue your files...
...Make an initial commit with Linear ID and the name of the issue using git commit --allow-empty -m Read the complete issue Reread the complete Issue and check if...
...the merge request Within your feature branch, merge the current master and push using: git pull origin master git push -u origin feature-branch-name You're encouraged to use...
...ID 1] My feature You can revert a single commit using the following syntax: git revert commit_sha2 To revert changes that are split across multiple commits, use the --no...
git revert --no-commit commit_sha3 git revert --no-commit commit_sha1 git commit -m "Revert Story...
Make sure you understand differences between git's areas (such as stash, workspace, upstream, etc.) and what commands affect which areas...
Grit gives you object oriented read/write access to Git repositories via Ruby...
...and were subsequently abandoned. We decided we wanted to clean up a bit, and git made that easy...
In your ~/.gitconfig: [core] editor=nano
...work? There is hope! The linked article tells how to recover from an accidental git reset --hard. On a Mac You will need to install GNU find utils as described...
...you select from a list of all started and finishes stories. Then it runs git commit with the generated message (i.e. all staged changes will be commited). When running for...
...we didn't lose any changes. Our solution is to clone the project's git repository into a folder inside a shared Dropbox folder...
...deploy new features but the latest commits are not ready for production? Then use git merge master~n to skip the n-last commits. Tip A big advantage of merging...
...duplicate commit messages in your history. Example It's time for a production deployment! git log --pretty=format:"%h - %s" --reverse origin/production..origin/master 0e6ab39f - Feature A 6396de5f - Feature B...
The ‘merge.*.driver` variable’s value is used to construct a command to run to merge ancestor’s version, current...
Optional further commit messages in the body Also see Howto: Write a proper git commit message To quickly generate such commit messages, add a new link "Commit" to your...
...title"]').innerText : story.querySelector('[name="story[name]"]').value); let id = story.dataset.id; if (id && title) { let gitptTitle = '[#' + id + '] ' + title; if (storyTitles.indexOf(gitptTitle) == -1) { storyTitles.push(gitptTitle); } } }); if (storyTitles.length > 0) { prompt('Your commit message...
...all minor and patch updates. Examples Bad source "https://rubygems.org" git_source(:github) { |repo| "https://github.com/#{repo}.git" } ruby "2.7.6" gem "rails", "~> 7.0.6" gem "sqlite3", "~> 1.4"
...remove this version constraint afterwards again. Good source "https://rubygems.org" git_source(:github) { |repo| "https://github.com/#{repo}.git" } ruby "2.7.6" gem "rails" gem "sqlite3" gem "puma"
RubyMine provides a visual tool for resolving merge conflicts locally. Follow Git > Resolve Conflicts in the context menu to open RubyMine's merge conflict tool. Left pane: local copy (read...
Some folks have started to keep their linux configuration in a git repository called "dotfiles". This sounds like a good idea. here are mine The idea is to keep all...
...config files in a ~/.dotfiles git repository, and symlink these files to all relevant places. This happens automatically with a rake task...
...included in diff Another is that now they will always be included in your git diff for merge requests. There are two options how you can address this:
...exclude from diff Luckily gitlab comes with a solution for this. You can ignore files for diffs within a project specific .gitattributes files like shown here: tmp/parallel_runtime_rspec.log -diff knapsack_rspec_report.json -diff...
git diff commit_hash -- path/to/file Provide any commit hashes or branch names like "master" for commit_hash...
...a web based code review system, facilitating online code reviews for projects using the Git version control system...
...on how the setup (with rbenv) might look like: # [...] RUN git clone --depth=1 https://github.com/rbenv/rbenv.git $HOME/.rbenv \ && git clone --depth=1 https://github.com/rbenv/ruby-build.git $HOME/.rbenv/plugins/ruby-build \ && echo 'eval "$(/root/.rbenv/bin/rbenv init...