What happens if repository has a remote under different name? #74
Comments
EDIT: with #80 being merged it's possible to run semantic-rs but it does not push any changes and also does not create a release on GitHub. I gave that issue some thought and my proposal here is to have a configuration file in place which denotes the remote to be used. The other option would be to ask the user but since the user is probably going to run semantic-rs multiple times they probably don't want to name the remote every time again. |
Also asking the user doens't make a lot of sense when semantic-rs is run on a CI server. |
So we could search for a remote="production" TODO for this one:
UPDATE: Updated to toml as suggested by @badboy. |
Why json? It's hard to write for a human. TOML is pretty much the go-to format in the Rust world and far easier to write. |
Right now we check for the remote
origin
. But in case the remote has a different name it's not possible to run semantic-rs right now.There should be a mechanism in place that allows users to run semantic-rs with a different remote than
origin
.The text was updated successfully, but these errors were encountered: