gitbutlerapp/gitbutler

Version 0.21.0 Operating System Windows Distribution Method msi (Windows) Describe the issue Any time I update gitbutler (from the toast message that appears when launching it), the installer automatically creates a desktop shortcut without asking. Could this be turned off please? How to reproduce (Optional) No response Expected behavior (Optional) No response Relevant log output (Optional)

What is the improvement or update you wish to see? Currently, GitButler supports AI providers including OpenAI, Anthropic, Ollama, and LM Studio for features like AI-generated commit messages and branch names. However, macOS users on Apple Silicon who use oMLX — a native MLX-based local LLM inference server — have no way to integrate it as an AI provider. There are two proposed improvements: Add native oMLX support as a dedicated AI provider option, similar to how Ollama and LM Studio are supported. oMLX is an open-source, Apple Silicon-optimized LLM inference server that exposes an OpenAI-compatible API endpoint, leverages Apple's MLX framework for high-performance inference, and features a native macOS menubar app for easy management. Add a generic "Custom OpenAI-compatible API" provider option, allowing users to specify any base URL and API key for any inference server that implements the OpenAI Chat Completions API specification. This would future-proof the AI provider sele

When a branch contains merge commits, the diff view shows all changes introduced by the merged branch rather than just the changes unique to the merge itself (conflict resolutions, manual edits). For example, merging origin/dev into a feature branch shows 65 changed files (+973/-3928) in GitButler, while GitHub shows 24 files for the same PR — because GitHub diffs against the merge-base. Root cause CommitDetails::from_commit_id() in crates/but-core/src/diff/commit_details.rs and commit_changes_with_line_stats_by_worktree_dir() in crates/but-core/src/diff/ui.rs both take only the first parent for diffing: let first_parent_commit_id = commit.parent_ids().map(|id| id.detach()).next(); For regular commits this is correct. For merge commits, the first parent is the branch being merged into, so the diff includes everything from the other branch. Proposed fix For commits with >1 parent, diff against the merge-base of the parents instead of the first parent. This shows only what the merge in

Version 0.19.5 Operating System macOS Distribution Method dmg (Mac OS - Apple Silicon) Describe the issue Summary but setup unconditionally overwrites pre-commit and post-checkout hooks without checking whether a hook manager (prek, pre-commit, husky, lefthook, etc.) already owns them. It renames existing hooks with a -user suffix and installs GITBUTLER_MANAGED_HOOK_V1 wrappers in their place. While but setup does print a note that it is "Installing Git hooks", it does not name the affected files, does not warn that existing hooks will be displaced, and does not detect pre-existing hook managers. The resulting state is fragile in several distinct ways. Failure modes 1. Insufficient warning on but setup but setup does print a note: Installing Git hooks to help manage commits on the workspace branch However it does not: Name which hook files will be affected (pre-commit, post-checkout) Mention that existing hooks will be renamed to a -user suffix Detect whether a hook manager (prek, p

but pr open # if there's only 1 and if that one has an attached pr but pr open [branch-id]