-
Notifications
You must be signed in to change notification settings - Fork 58
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
console log output after commit console output with aem up
in background
#2328
Comments
i actually think that the message is not needed altogether... i think if you checkout a new branch the proxy origin has to change but, i don't think this needs to happen with a commit. so maybe we can suppress this message if the origin actually hasn't changed. |
...or you just press |
🎉 This issue has been resolved in version 16.3.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
i am usually starting dev
aem up
and attach it to background withctrl-z
&bg
or start withaem up &
... then i am using thegit
cli tocommit
changes andpush
.after a
commit
there is some log output on the console... looks something like this, that is somewhat messing up my typing as it is usually a little bit delayed...as you can see i already started to type
git push origin
and that got mixed in thegit HEAD or remotes changed ...
message.i appreciate that this can happen with the above setup, it is just normally not super intrusive, but in this case it kind of gets me every time...
the simple solution would be to lower the log level on that specific message, but i am not sure if that's desired and i should just change how do things...
The text was updated successfully, but these errors were encountered: