Option to allow unlocking when working directory is not clean?
Open
feature
- Dominant language
- C++
- Stars
- 9.9k
- Forks
- 544
- PR merge metrics
- No merged PRs in 30d
Description
> Error: Working directory not clean.
Please commit your changes or 'git stash' them before running 'git-crypt unlock'.
Is it possible to add an option that allows unlocking when changes are not stashed? Would be useful for situations where changes are not related to encrypted files.
Contributor guide
Assessment
This issue has not been assessed yet.