Guest User

Untitled

a guest
May 25th, 2018
211
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 3.05 KB | None | 0 0
  1. [user]
  2. name = Justin Smestad
  3. email = justin.smestad@gmail.com
  4. [github]
  5. user = jsmestad
  6. token = # REMOVED
  7. [alias]
  8. ci = commit
  9. co = checkout
  10. f = fetch
  11. s = status
  12. b = branch
  13. d = diff
  14. a = add
  15. l = log
  16. [color]
  17. branch = auto
  18. diff = auto
  19. status = auto
  20. # [merge]
  21. # # Include the summary of merged commits into all newly created merge
  22. # # commits. The newly created merge commit will contain a one-line summary
  23. # # of every (well, most) merged commits.
  24. # log = true
  25. #
  26. # # Show merge statistics after merge.
  27. # stat = true
  28. [branch]
  29. # When creating a new branch off a remote branch, always set it up to
  30. # track the remote branch so that we can pull from there.
  31. autoseupmerge = always
  32. mergeoptions = --no-ff
  33. [branch "master"]
  34. # This is the list of cmdline options that should be added to git-merge
  35. # when I merge commits into the master branch.
  36. #
  37. # First off, the option --no-commit instructs git not to commit the merge
  38. # by default. This allows me to do some final adjustment to the commit log
  39. # message before it gets commited. I often use this to add extra info to
  40. # the merge message or rewrite my local branch names in the commit message
  41. # to branch names sensible to the casual reader of the git log.
  42. #
  43. # Option --no-ff instructs git to always record a merge commit, even if
  44. # the branch being merged into can be fast-forwarded. This is often the
  45. # case when you create a short-lived topic branch which tracks master, do
  46. # some changes on the topic branch and then merge the changes into the
  47. # master which remained unchanged while you were doing your work on the
  48. # topic branch. In this case the master branch can be fast-forwarded (that
  49. # is the tip of the master branch can be updated to point to the tip of
  50. # the topic branch) and this is what git does by default. With --no-ff
  51. # option set git creates a real merge commit which records the fact that
  52. # another branch was merged. I find this easier to understand and read in
  53. # the log.
  54. #mergeoptions = --no-commit --no-ff
  55. mergeoptions = --no-ff
Add Comment
Please, Sign In to add comment