v3.29.3

• changed: no longer publish RPM files with GitHub releases
• fixed: work around the parsing bug in git patch-id v2.46.1 (reported by @ilai-deutel)
• fixed: git machete git{hub,lab} create-{pr,mr} takes into account <!-- {start,end} git-machete generated --> in PR/MR template (suggested by @frank-west-iii)

v3.29.2

• changed: no longer publish Docker images

v3.29.1

• improved: git-machete delete-unmanaged uses the same algorithm as status and traverse to recognize merged branches (suggested by @cinnamennen)

v3.29.0

• added: git config keys machete.github.prDescriptionIntroStyle and machete.gitlab.mrDescriptionIntroStyle
• added: ability to turn off PR/MR description intro completely by setting the git config key to none (suggested by @tir38)
• added: ability to include downstream PRs/MRs in PR/MR description intro by setting the git config key to full (suggested by @aouaki)
• changed: layout and ordering of PRs/MRs in PR/MR description intro to better match git machete status

v3.28.0

• added: ability to specify pass-through flags in diff and log, for example git machete diff -- file.txt, git machete log -- --patch (partly contributed by @tdyas)

v3.27.0

• added: git config key http.sslVerify is honored when connecting to GitHub and GitLab APIs (suggested by @scamden)

v3.26.4

• fixed: avoid detecting a cycle when there's a PR/MR from main or master in a fork to the original repo (reported by @Joibel)
• fixed: git machete git{hub,lab} create-{pr,mr} no longer fails when creating a PR/MR across forks; instead, a forked PR is created (reported by @cspotcode)
• improved: git machete git{hub,lab} checkout-{prs,mrs} only adds annotations to affected branches (and not to every branch)

v3.26.3

• improved: performance of listing commits for red-edge branches on large repos
• improved: message in case of missing .git/machete file suggests to use git machete git{hub,lab} checkout-{prs,mrs}
• fixed: pass -c log.showSignature=false to all git invocations to hide GPG signatures in logs; if log.showSignature were set to a value equivalent to true in a user's git configuration, the GPG signatures shown in logs would cause errors in git log and git reflog parsing internal to git machete (reported and contributed by @goxberry)

v3.26.2

• fixed: parsing of multiline git config keys (reported by @saveman71)

v3.26.1

• fixed: readability of autogenerated PR/MR descriptions
• improved: git machete github restack-pr and git machete gitlab restack-mr fail on branches marked as push=no, instead of printing a warning and proceeding with retargeting anyway