Skip to content

bug(#83): fix stg pull when no upstream is configured #84

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

Conversation

NonLogicalDev
Copy link
Contributor

@NonLogicalDev NonLogicalDev commented Nov 20, 2020

CLOSES #83

@NonLogicalDev NonLogicalDev force-pushed the oleg.utkin/fix-pull-with-no-upstream branch 3 times, most recently from 6db174b to a4c9c0c Compare November 20, 2020 23:40
@NonLogicalDev NonLogicalDev force-pushed the oleg.utkin/fix-pull-with-no-upstream branch from a4c9c0c to e18c227 Compare November 24, 2020 07:25
@NonLogicalDev NonLogicalDev force-pushed the oleg.utkin/fix-pull-with-no-upstream branch from e18c227 to 36766f7 Compare November 24, 2020 07:50
@jpgrayson jpgrayson merged commit 15abb9f into stacked-git:master Dec 7, 2020
@jpgrayson
Copy link
Collaborator

Merged. I also pushed a follow-on change to correct a couple things.

Thank you for this PR!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

stg pull on a branch without upstream set is causing an Exception
2 participants