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

No output is shown for git-ps pull #13

Open
chillbrodev opened this issue Feb 26, 2020 · 5 comments
Open

No output is shown for git-ps pull #13

chillbrodev opened this issue Feb 26, 2020 · 5 comments
Labels
ready-for-dev Ready for Development

Comments

@chillbrodev
Copy link

chillbrodev commented Feb 26, 2020

When doing a git-ps pull there were new patches that it pulled down and added to the project. I only knew this because the dependency file changed and I was prompted. The fast forward/rebase output should be displayed.

$ git-ps pull
$.... empty

@drewdeponte
Copy link
Owner

@chillbrodev I understand you are expecting some sort of output but I am not 100% on what output you are expecting or think would be ideal here. Would you please elaborate on what your are envisioning here?

@drewdeponte
Copy link
Owner

git-ps pull is never fetching patches from upstream. It is fetching the latest code from origin/master and updating your origin/master to point to that latest point in the tree locally, and then it is rebasing your your stack of patches onto the updated origin/master.

@chillbrodev
Copy link
Author

@drewdeponte Sure thing, previously in beta versions of git-ps when you did a git-ps pull it would display the commit titles of the rebase, which would signify the applied changes.

@drewdeponte
Copy link
Owner

drewdeponte commented Feb 26, 2020

maybe that was just me allowing the output from git because I don't think I did anything specific there. So maybe this is just about allowing the output of the underlying git rebase come through. Or maybe allowing the output of both the git pull and the git rebase to come through.

@chillbrodev
Copy link
Author

Yea, that would be great to see that output.

@drewdeponte drewdeponte added the ready-for-dev Ready for Development label Mar 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready-for-dev Ready for Development
Projects
None yet
Development

No branches or pull requests

2 participants