CHANGELOG

v0.3.3 UNRELEASED

• Added forge-browse-remote to forge-dispatch. #477
• Depend on the Compat package, allowing me to use convenient features that were added to Emacs over the last few years, without having to wait another few years until everybody has updated to a reasonably recent Emacs release. 453c43f1e
• Added support for visiting the topic reference at point. #488
• Added forge-visit-topic to git-commit-mode-map. 05529a2a0
• Added new forge-post-dispatch prefix command, on C-c C-e, when editing posts. #497
• In topic buffers commits are now listed for merged pull-requests as well. a3cf64de6
• In topic buffers it is now shown whether a pull-requests is still a draft. 573e24156
• Added new command forge-edit-topic-draft, which toggles whether a pull-request is considered a draft, and new command forge-buffer-draft-p, which controls whether newly created pull-requests start out as drafts. #112, #517
• Added new hook forge-create-pullreq-hook. #512
• Remove support for obsolete libsqlite3 backend and broken sqlite3 backends. 45b06b801
• When checking out the branch corresponding to a pull-request, and that has already been created earlier, then it is now just check it out as-is. #519
• Added new command forge-rename-default-branch. 81e2bcd86
• Update the database before upgrading to a new schemata version. 2dc0a623c et al.
• Added new Git variable forge-forge.graphqlItemLimit, to limit the number of items per page, for Forge specifically. #543
• Pull-requests that have been deleted, but whose ref has been fetched, can be checked out now. e8523844d
• EmacSQL now automatically uses the best available backend (which allows for the removed option forge-database-connector). af9358dca

Bug fixes:

• d8773c8de, 0ca0ca8ac Fix handling of JSON and YAML booleans
• 44f01370f #481 Deal with yaml frontmatter missing title
• d04ab8f43 #482 forge-forge.remote: Show the dynamic fallback value
• 0ebd444a1 #485 forge–fetch-pullreq-target-repo: Fix copy-paste error
• 29fc13023 #494 Fix :initform form for sqlite-builtin and sqlite-module backends
• ec5f1656d..623be04aa Fix various Gitlab issues
• 422881e55 #549 Prevent post heading face from clobbering author & date faces
• 398ca3a17 Fix how Magit is kept usable when Forge database is inaccessible
• dc777b64a #588 Use color-values instead of deprecated x-color-values

Also contains various documentation updates, code clean-ups and build improvements.

v0.3.2 2022-03-07

• The command forge-toggle-display-in-status-buffer now affects all relevant sections. #470
• It is possible to create a pull-request from an existing issue again. #473

v0.3.1 2022-02-16

• Added several existing commands to forge-dispatch.
• Added new option forge-add-default-sections, which can be set to nil to prevent Forge from adding bindings to Magit keymaps and transient prefix commands.
• Added new command forge-browse-repository. #443
• Added new variable forge-format-avatar-function. #447
• Added support for the sqlite-builtin and sqlite-module backends. See magit/emacsql#86.
• Added new option forge-checkout-worktree-read-directory-function. #463
• Also included are many other improvements, updated documentation and bugfixes.

v0.3.0 2021-10-14

• Many actions that were surprisingly slow are much faster now, because an embarrassing bottleneck was removed in Closql v1.2.0.
• Added new option forge-database-connector allowing the use of other database connector libraries beside emacsql-sqlite (currently only emacsql-libsqlite3 (experimental) and emacsql-sqlite3 (discouraged)). bae6a527, 21720580
• Commands that take a topic or repository as argument now expect an object/row ID instead of an object or a number. Objects are not suitable as interactive arguments because their printed representation would be presented to the user when using repeat-complex-command, and because they might not reflect the current state when used like that. Numbers would be more readable and actually meaningful to humans, but additionally they would be ambiguous. Non-interactive functions continue to expect objects as arguments. #368
• Some essential key bindings that were somewhat randomly selected during initial development have now been changed for consistency, which I always intended to do, but did not get around to do until now. forge-dispatch is now bound to N instead of ~’~ and Forge’s bindings in magit-fetch and magit-pull now use N and n instead of Y and y. N was chosen because it was one of the last alphabetic keys available at the top-level in Magit. 8c9614e3 et al.
• Added new command forge-merge for merging pull-requests using the forge’s API, which I recommend you only use if someone forces you to do use the API. 3112aded
• Added support for following the links that some projects on Github display alongside issue templates. 46d5f253
• Setting the new Git variable forge.autoPull to false disables pulling Git data whenever API data is fetched. This may be useful in active mono-repos where there is always something new (but likely irrelevant) to pull. #362
• Added new commands forge-list-labeled-pullreqs and forge-list-labeled-issues. a3e6f8aa
• Starting with Emacs 28 bug-references is automatically configure for repositories cloned from many Git forges, so Forge no longer has to do it. #283, #412
• It is possible to fetch only select topics of a repository, which is useful if that happens to be large and/or if you are only interested in a select few topics (such as the one you are about to open). forge-pull learned to fetch information about the repository itself even when configured to only fetch certain topics. #382
• Added the forge-browse-* commands to forge-dispatch. #422
• Also included are several other improvements, updated documentation and bugfixes.

v0.2.1 2021-06-17

• Adjusted to breaking changes in EIEIO in Emacs 28.

v0.2.0 2021-05-25

• Second release.
• Features and bugfixes.
• I haven’t been keeping this list updated and don’t feel like going through hundreds of commits now. Sorry, maybe next time.

v0.1.0 2018-12-19

• Initial beta release.