Commitizen integration

[jukefr]

It would be nice to have commitizen integration, or a similar feature that allows you to use predefined commit messages.

For reference :

• https://github.com/commitizen/cz-cli
• https://github.com/commitizen/cz-conventional-changelog

[jesseduffield]

I'm thinking we could have a flag in the config that, when enabled, will use git cz over git commit, and unconditionally switch to a subprocess so that you can fill out the prompt. There's work in the gocui repo to enable showing the cz prompts inside of lazygit but it might take some time to properly get that over the line

[jesseduffield]

I've added this as a custom command in the Custom Commands Compendium, as a replacement for the default git commit behaviour upon pressing shift+c in the files panel.

There are quite a few upvotes on this one so if anybody had something different in mind, or thinks that this should work out of the box with lazygit, do let me know!

I'll close this ticket for now :)

[ceuk]

Great solution IMO

[rogerioefonseca]

Great solution IMO

Working nicely here, thanks @ceuk

[Cronos87]

I don't know if it's the place, but I wrote a simple command to have everything inside lazygit.

It could be enhanced; I wrote it down quickly for testing purposes 😊

Textes and style copied from vivaxy's extension (yeah, testing purposes…)

https://marketplace.visualstudio.com/items?itemName=vivaxy.vscode-conventional-commits

customCommands:
  - key: "C"
    command: 'git commit -m "{{ .Form.Type }}{{if .Form.Scopes}}({{ .Form.Scopes }}){{end}}: {{ .Form.Description }}"'
    description: "commit with commitizen"
    context: "files"
    prompts:
      - type: "menu"
        title: "Select the type of change you are committing."
        key: "Type"
        options:
          - name: "Feature"
            description: "a new feature"
            value: "feat"
          - name: "Fix"
            description: "a bug fix"
            value: "fix"
          - name: "Documentation"
            description: "Documentation only changes"
            value: "docs"
          - name: "Styles"
            description: "Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)"
            value: "style"
          - name: "Code Refactoring"
            description: "A code change that neither fixes a bug nor adds a feature"
            value: "refactor"
          - name: "Performance Improvements"
            description: "A code change that improves performance"
            value: "perf"
          - name: "Tests"
            description: "Adding missing tests or correcting existing tests"
            value: "test"
          - name: "Builds"
            description: "Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)"
            value: "build"
          - name: "Continuous Integration"
            description: "Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)"
            value: "ci"
          - name: "Chores"
            description: "Other changes that don't modify src or test files"
            value: "chore"
          - name: "Reverts"
            description: "Reverts a previous commit"
            value: "revert"
      - type: "input"
        title: "Enter the scope(s) of this change."
        key: "Scopes"
      - type: "input"
        title: "Enter the short description of the change."
        key: "Description"
      - type: "confirm"
        title: "Is the commit message correct?"
        body: "{{ .Form.Type }}{{if .Form.Scopes}}({{ .Form.Scopes }}){{end}}: {{ .Form.Description }}"