sonic-pi

https://github.com/sonic-pi-net/sonic-pi

C++

Code. Music. Live.

Rugged::Rebase.new

Initialize a new rebase operation. This will put +repo+ in a
rebase state.

+branch+ is the branch to be rebased, and +upstream+ is the branch
which is to be the new base. If +onto+ is specified, this will be
the one base, and +upstream+ is used to determine which commits
from +branch+ to use for the rebase.

You can pass merge and checkout options for the options hash, plus
a few rebase-specific ones:

:quiet ::
  If true, a flag will be set to ask tools to activate quiet
  mode. This does not do anything for libgit2/rugged but can be
  used to interact with other implementations.

:inmemory ::
  Do not put the repository in a rebase state but perform all the
  operations in-memory. In case of conflicts, the RebaseOperation
  returned by #next will contain the index which can be used to
  resolve conflicts.

:rewrite_notes_ref ::
  Name of the notes reference used to rewrite notes for rebased
  commits when finishing the rebase. If +nil+, it will be taken
  from the configuration.

Source | Google | Stack overflow

Edit

git clone [email protected]:sonic-pi-net/sonic-pi.git

cd sonic-pi

open app/server/ruby/vendor/rugged-1.7.1/ext/rugged/rugged_rebase.c

Contribute

# Make a new branch

git checkout -b -your-name--update-docs-Rugged--Rebase-new-for-pr

# Commit to git

git add app/server/ruby/vendor/rugged-1.7.1/ext/rugged/rugged_rebase.cgit commit -m "better docs for Rugged::Rebase.new"

# Open pull request

gem install hub # on a mac you can `brew install hub`

hub fork

git push <your name> -your-name--update-docs-Rugged--Rebase-new-for-pr

hub pull-request

# Celebrate!