buf icon indicating copy to clipboard operation
buf copied to clipboard

Add a --force flag to `buf push`

Open amckinney opened this issue 4 years ago • 0 comments

The primary use case would be to allow multiple commits with the same data.

amckinney avatar Aug 31 '21 18:08 amckinney

We don't need this now that users can push the same content with a new --tag (the new tag will point to the same commit ID). We can reopen this later if it's ever relevant again.

amckinney avatar Aug 11 '22 18:08 amckinney

We don't need this now that users can push the same content with a new --tag (the new tag will point to the same commit ID). We can reopen this later if it's ever relevant again.

I don't think this is the current behaviour, is it? i.e. when user push the same content with a new --tag, alreadyExists error will be returned and the new tag will not be created

cyinma avatar Aug 11 '22 18:08 cyinma

D'oh! You're right, I was mistaken - I just verified that behavior myself.

I think that we should actually create a new tag with the same commit ID though (like my original assumption), so maybe we should have a separate conversation elsewhere about that. What are your thoughts? I think it's better than creating a new commit (like the --force flag suggests), but I might be missing something.

amckinney avatar Aug 11 '22 19:08 amckinney

yeh that sounds like a reasonable behaviour to me (probably identify by a new flag so that it's not a breaking change?) we might create an internal ticket for that

cyinma avatar Aug 11 '22 19:08 cyinma