Conversation
ssickles
approved these changes
Oct 23, 2025
Member
ssickles
left a comment
ssickles
left a comment
There was a problem hiding this comment.
Seems like this would be the default. Would it make sense to that this like git does and provide a force option instead?
Contributor
Author
That's a good idea. |
BSick7
changed the title
--skip-when-exists flag to nullstone push--unique flag to nullstone push
Contributor
Author
|
@ssickles I took your idea and ran with it. Since |
ssickles
approved these changes
Oct 28, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This alters the default behavior of
nullstone pushto prevent version conflicts by skipping the push.This introduces a new flag,
--unique, to work as the CLI does today. This allows a user to push a new artifact with an incrementing-<count>suffix (if there's a conflict).