Make forbidden paths configurable #95
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Merged
tmeijn
pushed a commit
to tmeijn/dotfiles
that referenced
this pull request
Jun 20, 2025
This MR contains the following updates: | Package | Update | Change | |---|---|---| | [babarot/gomi](https://github.com/babarot/gomi) | patch | `v1.6.0` -> `v1.6.1` | MR created with the help of [el-capitano/tools/renovate-bot](https://gitlab.com/el-capitano/tools/renovate-bot). **Proposed changes to behavior should be submitted there as MRs.** --- ### Release Notes <details> <summary>babarot/gomi (babarot/gomi)</summary> ### [`v1.6.1`](https://github.com/babarot/gomi/blob/HEAD/CHANGELOG.md#v161---2025-06-19) [Compare Source](babarot/gomi@v1.6.0...v1.6.1) ##### New Features - Make forbidden paths configurable by [@​babarot](https://github.com/babarot) in babarot/gomi#95 - Customise styles on the filter matching/prompt by [@​babarot](https://github.com/babarot) in babarot/gomi#101 </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Enabled. ♻ **Rebasing**: Whenever MR is behind base branch, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this MR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this MR, check this box --- This MR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MC42MS4zIiwidXBkYXRlZEluVmVyIjoiNDAuNjEuMyIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOlsiUmVub3ZhdGUgQm90Il19-->
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What
forbidden_pathsoption to the trash config sectionWhy
This addresses issue #94 where the hardcoded forbidden paths were too restrictive for certain use cases. Users reported being unable to remove files in paths like
/var/tmp/and/usr/local/*.By making these paths configurable in
config.yaml, users can now customize which paths should be protected based on their specific needs, while still maintaining safety mechanisms where appropriate. This provides more flexibility for power users while preserving the default safety restrictions for most users.The default configuration still includes all the previous safety measures, ensuring that critical system directories remain protected unless explicitly configured otherwise.