CONTRIBUTING.md To see what you’ve changed but not yet staged, type git diff with no other arguments: $ git diff diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 8ebb991..643e24f 100644 --- a/CONTRIBUTING Date: Sat Mar 15 10:31:28 2008 -0700 Initial commit By default, with no arguments, git log lists the commits made in that repository in reverse chronological order; that is, the The git branch command does more than just create and delete branches. If you run it with no arguments, you get a simple listing of your current branches: $ git branch iss53 * master testing Notice

modified: CONTRIBUTING.md To see what you’ve changed but not yet staged, type git diff with no other arguments: $ git diff diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 8ebb991..643e24f 100644 --- a/CONTRIBUTING Date: Sat Mar 15 10:31:28 2008 -0700 Initial commit By default, with no arguments, git log lists the commits made in that repository in reverse chronological order; that is, the The git branch command does more than just create and delete branches. If you run it with no arguments, you get a simple listing of your current branches: $ git branch iss53 * master testing Notice

CONTRIBUTING.md To see what you’ve changed but not yet staged, type git diff with no other arguments: $ git diff diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 8ebb991..643e24f 100644 --- a/CONTRIBUTING Date: Sat Mar 15 10:31:28 2008 -0700 Initial commit By default, with no arguments, git log lists the commits made in that repository in reverse chronological order; that is, the The git branch command does more than just create and delete branches. If you run it with no arguments, you get a simple listing of your current branches: $ git branch iss53 * master testing Notice