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

CLI push - change behavior pushing TM with same content #81

Open
enricoschuetz opened this issue Mar 4, 2024 · 0 comments
Open

CLI push - change behavior pushing TM with same content #81

enricoschuetz opened this issue Mar 4, 2024 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@enricoschuetz
Copy link
Contributor

Current behavior:

When pushing a TM that already exists with the same content and version,
the push is rejected if the same TM (same digest) has the latest timestamp in history. (OK).

When pushing a TM that already exists with the same content and version,
but the same TM (same digest) has not the latest timestamp in history, then the push is simply accepted.

Although it makes sense to "reset" a specific content from point of timestamp, this could be a bit confusing
when the behavior differs.

Expected behavior (proposal):

When pushing a TM that already exists with the same content and version,
the push is default rejected.

Only by passing a --force flag, the TM with same content and version can be pushed,
so it has the latest timestamp in history.

@enricoschuetz enricoschuetz added the enhancement New feature or request label Mar 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants