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

uncommitted history has unexpected implications for bundle naming #114

Closed
kyocum opened this issue Jul 24, 2019 · 1 comment
Closed

uncommitted history has unexpected implications for bundle naming #114

kyocum opened this issue Jul 24, 2019 · 1 comment
Labels
bug Something isn't working enhancement New feature or request

Comments

@kyocum
Copy link
Owner

kyocum commented Jul 24, 2019

The uncommitted history currently maintains a maximum of N uncommitted bundles with the same human name. This can have the unintended consequence of deleting bundles needed by downstream tasks if users do not assign unique human names to the bundles. Note that, if the user does not set the human name in pipe_requires, then this shouldn't be an issue. But what we need to determine is a.) whether an uncommitted history is important to keep as a feature and b.) if so, is there a more intuitive mode of operation.

@kyocum kyocum added bug Something isn't working enhancement New feature or request labels Jul 24, 2019
@kyocum
Copy link
Owner Author

kyocum commented Mar 13, 2020

Uncommitted history has been retired as a feature.

@kyocum kyocum closed this as completed Mar 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant