We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
As mentioned in #2459 fsck --decrypt does not honor core.autosync config set to false
fsck --decrypt
core.autosync
false
gopass config core.autosync false //gopass config core.autoimport false //not relevant //verified config is set gopass fsck --decrypt
should honor config and not push to git repo, manual sync should be needed after fsck
core.autoimport config works as expected
core.autoimport
The text was updated successfully, but these errors were encountered:
The setting should be honored. If not it's a bug.
I'll try to reproduce and if I can it should be easy to fix.
Sorry, something went wrong.
Honor core.autosync for all current git push operations
fa39ff9
Fixes gopasspw#2495 RELEASE_NOTES=[BUGFIX] Honor core.autosync Signed-off-by: Dominik Schulz <dominik.schulz@gauner.org>
Honor core.autosync for all current git push operations (#2497)
f63c2d1
Fixes #2495 RELEASE_NOTES=[BUGFIX] Honor core.autosync Signed-off-by: Dominik Schulz <dominik.schulz@gauner.org> Signed-off-by: Dominik Schulz <dominik.schulz@gauner.org>
dominikschulz
Successfully merging a pull request may close this issue.
Summary
As mentioned in #2459
fsck --decrypt
does not honorcore.autosync
config set tofalse
Steps To Reproduce
gopass config core.autosync false
//gopass config core.autoimport false //not relevant
//verified config is set
gopass fsck --decrypt
Expected behavior
should honor config and not push to git repo, manual sync should be needed after fsck
Environment
Additional context
core.autoimport
config works as expectedThe text was updated successfully, but these errors were encountered: