Skip to content
New issue

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

change sourmash sig manifest to not regenerate a manifest by default #2034

Open
ctb opened this issue May 5, 2022 · 0 comments · May be fixed by #3074
Open

change sourmash sig manifest to not regenerate a manifest by default #2034

ctb opened this issue May 5, 2022 · 0 comments · May be fixed by #3074
Labels
5.0 issues to address for a 5.0 release
Milestone

Comments

@ctb
Copy link
Contributor

ctb commented May 5, 2022

For some reason I thought it was a good idea to have sig manifest iterate over the signatures to generate a new manifest by default, unless you specify --no-rebuild-manifest.

It turns out it's really annoying now that I'm using sig manifest for all sorts of other things.

@ctb ctb added the 5.0 issues to address for a 5.0 release label May 5, 2022
@luizirber luizirber added this to the 5.0 milestone Dec 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
5.0 issues to address for a 5.0 release
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants