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

cloudup should only create & update one bitbucket repo per github repo #86

Closed
westonganger opened this issue Jul 21, 2017 · 3 comments

Comments

Projects
None yet
2 participants
@westonganger
Copy link

commented Jul 21, 2017

Issue Label:

  • Bug
  • New feature
  • Enhancement
  • New component

Description:
Currently cloudup creates repos with timestamped names. So every time you backup it creates a new repo for the new timestamp. It would be much more preferable to have it backup the repo with the same name as github (ie. Bash-Snippets --> Bash-Snippets) and continuously apply updates to the 1 bitbucket repo.

@alexanderepstein

This comment has been minimized.

Copy link
Owner

commented Jul 22, 2017

Added with c1b3016

Works by changing the default behavior to the one stated in the issue and then making the current default behavior an option. By using -t it will append the a timestamp to the repo name always guaranteeing a unique bitbucket repository. Without the use of the -t option it will set the remote url to just the project name. This in turn will either create a new repo (if it doesn't already exist) and then push the changes.

@alexanderepstein

This comment has been minimized.

Copy link
Owner

commented Jul 22, 2017

Released in Version 1.14.0

@alexanderepstein

This comment has been minimized.

Copy link
Owner

commented Jul 22, 2017

Fixed all bugs related to this with Version 1.14.2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.