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.

Sign up for GitHub

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

Jump to bottom

deprecate: why depracate an entire model/artifact? #430

Open
dberenbaum opened this issue Oct 30, 2023 · 1 comment
Open

deprecate: why depracate an entire model/artifact? #430

dberenbaum opened this issue Oct 30, 2023 · 1 comment
Labels
question Further information is requested

Comments

@dberenbaum
Copy link
Contributor

It's unclear to me the value of deprecating an entire model/artifact. Why is it not enough to unassign a stage or archive the git repo? I get confused with what this is supposed to do in gto and studio. Is there a known workflow where it is helpful/needed?
@shcheklein
Copy link
Member

It disappears from the MR then. If you just unassign it you can still see it. You can't archive the whole if this is a monorepo, or you have an older model in your history that you don't want to see anymore.

@shcheklein shcheklein added the question Further information is requested label Nov 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
question Further information is requested
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dberenbaum @shcheklein