This release comes with only two minor bug fixes. However, there are also multiple process and non-feature changes that I’d like to formally announce. They will optimize the feedback loop and accelerate future improvements to hopefully attract more contributors to this project 🥳.

Bugs fixed

• Tilde (~) from current token not expanding for search files (#109 - @kidonng)
• Search shell variables returning status code 0 when actually, it errored (#82)

Non-feature improvements

Continuous integration

fzf.fish now has automated test and continuous integration now! It’s hard to understate how excited I am about this! When I first started fzf.fish and pushed a number of bugs because I didn’t have automated tests, I was so frustrated but didn’t think it was possible to test a shell workflow involving user input into an external program. But since then, a confluence of technologies have emerged to made it feasible: GitHub Actions, fishtape, clownfish, and fzf’s built in scripting mode.
Special thanks to @jorgebucaran and @IlanCosman for help in accomplishing this major milestone!

GitHub Wiki opened

The troubleshooting and prior art sections of the readme has moved to the Wiki.
The goal is to make maintaining Q&A style help a lightweight process. Having to commit to master is troublesome and people likely don't care to see those changes when they check the commit log. Furthermore, I have been hindered from writing a more in-depth documentation but I didn't want the readme to be hard to scroll through. Moving these sections to the readme will resolve that tension.

Non-bug issues -> GitHub Discussions

• Most non-bug issues have been moved to the repo discussions (so if you can't find your old issue, try the discussions).
• Additionally, the issue template choose has been configured to direct all future questions or feature requests to the discussions.
• Bug reports are now the only type of issue that users can file. I added a template to help make this more obvious and collect higher quality bug reports.

The motivation of this change is to make common questions and feature ideas more discoverable and help coalesce discussion on them, which will reduce the amount of work I have to do addressing common questions and features. This will also help me get a better picture overall of how users use fzf.fish, leading to more informed decisions.

The issue template chooser was copied from starship. Thanks @matchai for help with pre-populating discussions with a category.