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.

Sign up for GitHub

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

Jump to bottom

git:ensure_pushed needs to be more robust #639

Closed
zhou-daniel-dz opened this issue Feb 21, 2019 · 0 comments · Fixed by #677
Closed

git:ensure_pushed needs to be more robust #639

zhou-daniel-dz opened this issue Feb 21, 2019 · 0 comments · Fixed by #677
Labels
bug
Milestone
1.3.0

Comments

@zhou-daniel-dz
Copy link

Currently the git:ensure_pushed task does not account for the case where a remote branch doesn't exist while a local branch does.

As a result git:ensure_pushed does not exit properly.

Ensuring everyting is pushed to git fatal: ambiguous argument 'origin/remote_branch': unknown revision or path not in the working tree.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
1.3.0
Development

Successfully merging a pull request may close this issue.

Ensure branch exists locally and remotely before comparing it mina-deploy/mina
2 participants
@zhou-daniel-dz @lovro-bikic