• Icon: Suggestion Suggestion
    • Resolution: Fixed
    • 1.5.4
    • Git
    • None
    • all
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      It would be nice to have a checkbox in the commit view (or a prompt when the commit fails, due to pre-commit hooks) to force the commit (-n flag)

      GitX (http://gitx.laullon.com/) has this option.

      Example of how this works on the command line:

      $ git commit -m "Added Readme file"
      Pre-Commit message hook failed!
      $ git commit -nm "Added Readme file"
      [master 2db5767] Added Readme file
      1 files changed, 1 insertions, 0 deletions
      create mode 100644 README
      $

            [SRCTREE-1011] Force commit

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3371746 ] New: JAC Suggestion Workflow 3 [ 3671955 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Monique Khairuliana (Inactive) made changes -
            Workflow Original: SourceTree Bug Workflow [ 382741 ] New: JAC Suggestion Workflow [ 3371746 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Monique Khairuliana (Inactive) made changes -
            Issue Type Original: New Feature [ 2 ] New: Suggestion [ 10000 ]
            Brian Ganninger (Inactive) made changes -
            Assignee Original: KieranA [ ksenior ]
            KieranA made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: Open [ 1 ] New: Closed [ 6 ]

            KieranA added a comment -

            An option to bypass commit hooks has been added to the commit dialog which uses the --no-verify Git flag

            KieranA added a comment - An option to bypass commit hooks has been added to the commit dialog which uses the --no-verify Git flag

            Ian Suda added a comment -

            Yes, sorry, "Force" is what GitX called it, but it is really for the --no-verify flag.

            Ian Suda added a comment - Yes, sorry, "Force" is what GitX called it, but it is really for the --no-verify flag.

            KieranA added a comment -

            Whilst you mention "force", this isn't to be confused with the push --force flag, the -n in commit is for --no-verify

            KieranA added a comment - Whilst you mention "force", this isn't to be confused with the push --force flag, the -n in commit is for --no-verify
            KieranA made changes -
            Assignee Original: Steve Streeting [ sstreeting ] New: KieranA [ ksenior ]
            Steve Streeting (Inactive) made changes -
            Fix Version/s New: 1.5.4 [ 27900 ]
            Fix Version/s Original: 1.5.3 [ 27890 ]

              Unassigned Unassigned
              4db43ceb1ff8 Ian Suda
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: