Skip to content

Link to, or incorporate (parts) of website https://git-rebase.io/ #1329

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

Closed
HonkingGoose opened this issue Nov 6, 2019 · 0 comments · Fixed by #1449
Closed

Link to, or incorporate (parts) of website https://git-rebase.io/ #1329

HonkingGoose opened this issue Nov 6, 2019 · 0 comments · Fixed by #1449

Comments

@HonkingGoose
Copy link
Contributor

Which version of the book is affected?

Problem is present in source files.

Describe the bug:

I think the guidance on git rebase in the Pro Git book is not enough to actually learn how to use git rebase to perform the common operations like squashing commits, rebasing from upstream branch, reordering commits, fixing up unneeded commits.

Steps to reproduce:

This is a bit cheeky, so don't take this too seriously please. 😸

  1. Try to learn how to use git rebase from Pro Git book.
  2. Fail.
  3. Read https://git-rebase.io/
  4. Succeed in using git rebase.

Expected behavior:

After reading the parts: https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History and https://git-scm.com/book/en/v2/Git-Branching-Rebasing the reader should be able to actually perform the mentioned commands for themselves in a real workflow.

Screenshots:

Additional context:

I found the website https://git-rebase.io/ to be extremely helpful to practice with git rebase. The examples are well written, easy to follow.

I think the Pro Git book would benefit massively from a guided "sandbox" tutorial on rewriting history.

I think the range of options are:

  • Ask permission to link to the website.
  • Ask permission to write our own examples, based on the work on the webpage.
  • Ask permission to wholesale incorporate parts/the whole text in the book.
  • Do a "clean room design" by letting someone write a tutorial on rewriting Git history, without ever having looked at the linked website.

I'll leave it up to the Pro Git maintainers to decide what/if action should be taken.

Related issue: #1247

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant