aboutsummaryrefslogtreecommitdiff
path: root/docs
AgeCommit message (Collapse)Author
2025-05-01Release version 4.3.3v4.3.3Jonas Bernoulli
2025-04-19magit-diff-visit-file: Remove inaccurate sentence from documentationRichard Sent
Co-authored-by: Jonas Bernoulli <jonas@bernoul.li>
2025-04-19Regenerate manualJonas Bernoulli
2025-04-15git-rebase-kill-line: If the line is commented then uncomment itJonas Bernoulli
2025-04-01Release version 4.3.2v4.3.2Jonas Bernoulli
2025-04-01Regenerate manualJonas Bernoulli
2025-03-31magit-rebase-autosquash: With a prefix allow selecting beginningJonas Bernoulli
2025-03-25magit-merge-into: Rename to magit-merge-dissolve and change bindingJonas Bernoulli
Use the term "dissolve" because that makes it clear that the branch that is being merged is also deleted afterwards. Also change the key binding in the `magit-merge' menu, to keep it mnemonic. At least the latter was planned since [1: 4c096921fd]. Do not define `magit-merge-into' as an obsolete alias, since that would prolong the period during which some users would by take by surprise. Re #4386. 1: 2021-07-01 4c096921fda97ebdff656a35a257910fca9e5aad magit-merge: Change magit-merge-into's description
2025-03-02Release version 4.3.1v4.3.1Jonas Bernoulli
2025-03-01AUTHORS.md: Update list of contributorsJonas Bernoulli
2025-02-23changelog: Fix typoJonas Bernoulli
2025-02-23changelog: Fix typosJonas Bernoulli
2025-02-10magit-diff-wash-submodule: Use magit-format-file-functionJonas Bernoulli
2025-02-08magit-format-file-function: New optionJonas Bernoulli
Closes #5308.
2025-02-04Release version 4.3.0v4.3.0Jonas Bernoulli
2025-02-04Bump copyright yearsJonas Bernoulli
2025-02-03Drop dependency on DashJonas Bernoulli
2025-02-03Complete dependency listsJonas Bernoulli
2025-02-03manual: Update a pathJonas Bernoulli
2025-02-02manual: Drop a repeated paragraphKyle Meyer
2025-02-02manual: Fix a typoKyle Meyer
2025-02-01AUTHORS.md: Update list of contributorsJonas Bernoulli
2025-01-30Speed up Git's part in listing files in status bufferJonas Bernoulli
In [1: 83d89ee5bb] we did speed up Magit's part in this task, but also removed optimization used to speed up Git's part. Bring those back. Also respect all local values of `status.showUntrackedFiles' again. Closes #5298. 1: 2025-01-27 83d89ee5bb1c488544bae60d52f7ee1987b6449e Speed up and simplify listing files in status buffer
2025-01-27AUTHORS.md: Update list of contributorsJonas Bernoulli
2025-01-27Speed up and simplify listing files in status bufferJonas Bernoulli
2025-01-27manual: Split up "Status Sections" sectionJonas Bernoulli
2025-01-19manual: Fix pastoJonas Bernoulli
2025-01-17manual: Fix introduction to committingJonas Bernoulli
We do call `git commit' with arguments, just not with `--message'.
2025-01-17manual: Categorize "Options used by commit commands" sectionJonas Bernoulli
2025-01-17Improve documentation about commit commandsJonas Bernoulli
2025-01-17Rearrange definitions and documentation of commit commandsJonas Bernoulli
Rearrange their definitions and the order in which they are described in the manual, to better mirror their new arrangement in the menu.
2025-01-17magit-commit-{alter,revise}: New commandsJonas Bernoulli
- Bind "A" to `magit-commit-alter'. Previously that was bound to `magit-commit-augment', but the new command is more similar to `magit-commit-amend', whose binding is "a". `amend' and `alter' do the approximately same thing, but the former is limited to the "HEAD" commit. Additionally `alter' needs changes (else use `revise'). - Bind "W" to `magit-commit-revise' because "w" is bound to `magit-commit-reword' and these two are also HEAD/any variants. - Bind "n" to `magit-commit-augment'. The mnemonic being that this adds a "note", which we later have to take into account when writing the final commit message. - Bind "d" to `magit-commit-reshelve' because "n" is now taken. Use "d" because it changes dates. This command is disabled by default. - In the menu, arrange the variants in a way that hopefully makes these relations more obvious. Unfortunately this is not possible without leaving some "table cells" empty.
2025-01-17magit-commit-create: No longer amend with a prefix argumentJonas Bernoulli
Several fine commands dedicated to amending exist, and have been preferable to this prefix argument for many years now.
2025-01-04magit-status-show-untracked-files: New optionJonas Bernoulli
2025-01-04magit-insert-untracked-files: Fix use of status.showUntrackedFilesJonas Bernoulli
Previously the meanings of "normal" and "all" were inverted. Now "all" means "show all untracked" files, just like for `git status'. "normal" means "show untracked files and directories", but while in the case of `git status' that means that individual non-top-level files are never shown, in our case directory sections can be expanded on demand to show them when needed.
2025-01-02magit-stash--apply-1: Improve presentation of fallback methodsJonas Bernoulli
Be more verbose about the available fallback methods and also let the user abort. Re #5253.
2025-01-01Release version 4.2.0v4.2.0Jonas Bernoulli
2025-01-01Regenerate manualJonas Bernoulli
2025-01-01Bump copyright yearsJonas Bernoulli
2024-12-23manual: Copyedit FAQ a bitJonas Bernoulli
2024-12-23manual: Fix two urlsJonas Bernoulli
2024-12-23magit-toggle-subprocess-record: New commandJonas Bernoulli
This is a refinement of the functionality, which was previously enabled using the variable `magit-process-extreme-logging' (which we remove).
2024-12-23magit-toggle-git-debug: Improve documentationJonas Bernoulli
Focus on documenting the command `magit-toggle-git-debug', at the expense of the documentation for the variable `magit-git-debug', which users don't really have to know about.
2024-12-19magit-toggle-profiling: New commandJonas Bernoulli
2024-12-19manual: Document magit-profile-refresh-bufferJonas Bernoulli
2024-12-19magit-diff-dwim: Improve documentationJonas Bernoulli
I wrote this a while ago in response to a user complaining that this command never does what they mean (dwtm), and have finally decided to install it after all, because, despite the slight saltiness towards the end, this actually is useful information.
2024-12-06Release version 4.1.3v4.1.3Jonas Bernoulli
2024-12-03Fix typos in changelogJonas Bernoulli
2024-11-26magit-stash-{pop,apply}: Stop after successfully installing conflictJonas Bernoulli
If we cannot successfully install the conflict with "git stash apply --index", we also try "git stash apply", and if that fails as well, we continue with "git apply --3way". That assumed that we could tell whether a stash was either applied with no conflict or the conflict was successfully installed by, or else the conflict could not be installed, by checking status. Unfortunately it turns out that the exit status is also 1 if the conflict was successfully installed. Instead we have to look at the output. Unfortunately we can only do that for Git v2.38.0 and later, and have to fall back to the less convenient behavior provided by Git itself. Closes #5253.
2024-11-26magit-stash-{pop,apply}: Copy edit documentationJonas Bernoulli