Git config --global

    show git config settings
    view git config values
    see git config options
    git show config parameters
  • Show git config settings
  • Git config --list...

    8.1 Customizing Git - Git Configuration

    Server Configuration

    Not nearly as many configuration options are available for the server side of Git, but there are a few interesting ones you may want to take note of.

    Git is capable of making sure every object received during a push still matches its SHA-1 checksum and points to valid objects.

    Git config remove

  • Git config remove
  • Git config username and password
  • Git config --list
  • Git config show username
  • Git config user.name and email
  • However, it doesn’t do this by default; it’s a fairly expensive operation, and might slow down the operation, especially on large repositories or pushes. If you want Git to check object consistency on every push, you can force it to do so by setting to true:

    Now, Git will check the integrity of your repository before each push is accepted to make sure faulty (or malicious) clients aren’t introducing corrupt data.

    If you rebase commits that you’ve already pushed and then try to push again, or otherwise try to push a commit to a remote branch that doesn’t contain the commit that the remote branch currently points to, you’ll be denied.

    This is generally good policy; but in the case of the rebase, you may determine that you know what you

      show all git config values
      git config show current settings