GIT-COMMIT(1)                               Git Manual                              GIT-COMMIT(1)

       git-commit - Record changes to the repository

       git commit [-a | --interactive | --patch] [-s] [-v] [-u] [--amend]
                  [--dry-run] [(-c | -C | --fixup | --squash) ]
                  [-F  | -m ] [--reset-author] [--allow-empty]
                  [--allow-empty-message] [--no-verify] [-e] [--author=]
                  [--date=] [--cleanup=] [--[no-]status]
                  [-i | -o] [-S[]] [--] [...]

       Stores the current contents of the index in a new commit along with a log message from the
       user describing the changes.

       The content to be added can be specified in several ways:

        1. by using git add to incrementally "add" changes to the index before using the commit
           command (Note: even modified files must be "added");

        2. by using git rm to remove files from the working tree and the index, again before
           using the commit command;

        3. by listing files as arguments to the commit command, in which case the commit will
           ignore changes staged in the index, and instead record the current content of the
           listed files (which must already be known to Git);

        4. by using the -a switch with the commit command to automatically "add" changes from all
           known files (i.e. all files that are already listed in the index) and to automatically
           "rm" files in the index that have been removed from the working tree, and then perform
           the actual commit;

        5. by using the --interactive or --patch switches with the commit command to decide one
           by one which files or hunks should be part of the commit, before finalizing the
           operation. See the “Interactive Mode” section of git-add(1) to learn how to operate
           these modes.

       The --dry-run option can be used to obtain a summary of what is included by any of the
       above for the next commit by giving the same set of parameters (options and paths).

       If you make a commit and then find a mistake immediately after that, you can recover from
       it with git reset.

       -a, --all
           Tell the command to automatically stage files that have been modified and deleted, but
           new files you have not told Git about are not affected.

       -p, --patch
           Use the interactive patch selection interface to chose which changes to commit. See
           git-add(1) for details.

       -C , --reuse-message=
           Take an existing commit object, and reuse the log message and the authorship
           information (including the timestamp) when creating the commit.

       -c , --reedit-message=
           Like -C, but with -c the editor is invoked, so that the user can further edit the
           commit message.

           Construct a commit message for use with rebase --autosquash. The commit message will
           be the subject line from the specified commit with a prefix of "fixup! ". See git-
           rebase(1) for details.

           Construct a commit message for use with rebase --autosquash. The commit message
           subject line is taken from the specified commit with a prefix of "squash! ". Can be
           used with additional commit message options (-m/-c/-C/-F). See git-rebase(1) for

           When used with -C/-c/--amend options, or when committing after a a conflicting
           cherry-pick, declare that the authorship of the resulting commit now belongs to the
           committer. This also renews the author timestamp.

           When doing a dry-run, give the output in the short-format. See git-status(1) for
           details. Implies --dry-run.

           Show the branch and tracking info even in short-format.

           When doing a dry-run, give the output in a porcelain-ready format. See git-status(1)
           for details. Implies --dry-run.

           When doing a dry-run, give the output in a the long-format. Implies --dry-run.

       -z, --null
           When showing short or porcelain status output, terminate entries in the status output
           with NUL, instead of LF. If no format is given, implies the --porcelain output format.

       -F , --file=
           Take the commit message from the given file. Use - to read the message from the
           standard input.

           Override the commit author. Specify an explicit author using the standard A U Thor
            format. Otherwise  is assumed to be a pattern and is used
           to search for an existing commit by that author (i.e. rev-list --all -i
           --author=); the commit author is then copied from the first such commit found.

           Override the author date used in the commit.

       -m , --message=
           Use the given  as the commit message. If multiple -m options are given, their
           values are concatenated as separate paragraphs.

       -t , --template=
           When editing the commit message, start the editor with the contents in the given file.
           The commit.template configuration variable is often used to give this option
           implicitly to the command. This mechanism can be used by projects that want to guide
           participants with some hints on what to write in the message in what order. If the
           user exits the editor without editing the message, the commit is aborted. This has no
           effect when a message is given by other means, e.g. with the -m or -F options.

       -s, --signoff
           Add Signed-off-by line by the committer at the end of the commit log message. The
           meaning of a signoff depends on the project, but it typically certifies that committer
           has the rights to submit this work under the same license and agrees to a Developer
           Certificate of Origin (see http://developercertificate.org/ for more information).

       -n, --no-verify
           This option bypasses the pre-commit and commit-msg hooks. See also githooks(5).

           Usually recording a commit that has the exact same tree as its sole parent commit is a
           mistake, and the command prevents you from making such a commit. This option bypasses
           the safety, and is primarily for use by foreign SCM interface scripts.

           Like --allow-empty this command is primarily for use by foreign SCM interface scripts.
           It allows you to create a commit with an empty commit message without using plumbing
           commands like git-commit-tree(1).

           This option determines how the supplied commit message should be cleaned up before
           committing. The  can be strip, whitespace, verbatim, scissors or default.

               Strip leading and trailing empty lines, trailing whitespace, commentary and
               collapse consecutive empty lines.

               Same as strip except #commentary is not removed.

               Do not change the message at all.

               Same as whitespace, except that everything from (and including) the line "#
               ------------------------ >8 ------------------------" is truncated if the message
               is to be edited. "#" can be customized with core.commentChar.

               Same as strip if the message is to be edited. Otherwise whitespace.

           The default can be changed by the commit.cleanup configuration variable (see git-

       -e, --edit
           The message taken from file with -F, command line with -m, and from commit object with
           -C are usually used as the commit log message unmodified. This option lets you further
           edit the message taken from these sources.

           Use the selected commit message without launching an editor. For example, git commit
           --amend --no-edit amends a commit without changing its commit message.

           Replace the tip of the current branch by creating a new commit. The recorded tree is
           prepared as usual (including the effect of the -i and -o options and explicit
           pathspec), and the message from the original commit is used as the starting point,
           instead of an empty message, when no other message is specified from the command line
           via options such as -m, -F, -c, etc. The new commit has the same parents and author as
           the current one (the --reset-author option can countermand this).

           It is a rough equivalent for:

                       $ git reset --soft HEAD^
                       $ ... do something else to come up with the right tree ...
                       $ git commit -c ORIG_HEAD

           but can be used to amend a merge commit.

           You should understand the implications of rewriting history if you amend a commit that
           has already been published. (See the "RECOVERING FROM UPSTREAM REBASE" section in git-

           Bypass the post-rewrite hook.

       -i, --include
           Before making a commit out of staged contents so far, stage the contents of paths
           given on the command line as well. This is usually not what you want unless you are
           concluding a conflicted merge.

       -o, --only
           Make a commit by taking the updated working tree contents of the paths specified on
           the command line, disregarding any contents that have been staged for other paths.
           This is the default mode of operation of git commit if any paths are given on the
           command line, in which case this option can be omitted. If this option is specified
           together with --amend, then no paths need to be specified, which can be used to amend
           the last commit without committing changes that have already been staged.

       -u[], --untracked-files[=]
           Show untracked files.

           The mode parameter is optional (defaults to all), and is used to specify the handling
           of untracked files; when -u is not used, the default is normal, i.e. show untracked
           files and directories.

           The possible options are:

           ·   no - Show no untracked files

           ·   normal - Shows untracked files and directories

           ·   all - Also shows individual files in untracked directories.

               The default can be changed using the status.showUntrackedFiles configuration
               variable documented in git-config(1).

       -v, --verbose
           Show unified diff between the HEAD commit and what would be committed at the bottom of
           the commit message template to help the user describe the commit by reminding what
           changes the commit has. Note that this diff output doesn’t have its lines prefixed
           with #. This diff will not be a part of the commit message.

           If specified twice, show in addition the unified diff between what would be committed
           and the worktree files, i.e. the unstaged changes to tracked files.

       -q, --quiet
           Suppress commit summary message.

           Do not create a commit, but show a list of paths that are to be committed, paths with
           local changes that will be left uncommitted and paths that are untracked.

           Include the output of git-status(1) in the commit message template when using an
           editor to prepare the commit message. Defaults to on, but can be used to override
           configuration variable commit.status.

           Do not include the output of git-status(1) in the commit message template when using
           an editor to prepare the default commit message.

       -S[], --gpg-sign[=]
           GPG-sign commits. The keyid argument is optional and defaults to the committer
           identity; if specified, it must be stuck to the option without a space.

           Countermand commit.gpgSign configuration variable that is set to force each and every
           commit to be signed.

           Do not interpret any more arguments as options.

           When files are given on the command line, the command commits the contents of the
           named files, without recording the changes already staged. The contents of these files
           are also staged for the next commit on top of what have been staged before.

       The GIT_AUTHOR_DATE, GIT_COMMITTER_DATE environment variables and the --date option
       support the following date formats:

       Git internal format
           It is  


Designed by SanjuD(@ngineerbabu)