We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I think it would be useful to print a diff when a tracked branch is updated. Current behaviour:
pkg> add BenchmarkTools#master # change the master branch pkg> up [...] Updating `~/.julia/environments/v0.7/Project.toml` [6e4b80f9] ~ BenchmarkTools v0.2.5+ #master Updating `~/.julia/environments/v0.7/Manifest.toml` [6e4b80f9] ~ BenchmarkTools v0.2.5+ #master
which IMO would be better as
pkg> up [...] Updating `~/.julia/environments/v0.7/Project.toml` [6e4b80f9] ↑ BenchmarkTools v0.2.5+ #master(commit1) ⇒ v0.2.5+ #master(commit2) Updating `~/.julia/environments/v0.7/Manifest.toml` [6e4b80f9] ↑ BenchmarkTools v0.2.5+ #master(commit1) ⇒ v0.2.5+ #master(commit2)
Additionally, perhaps we should always print the commit hash for tracked branches, e.g. st would change from
st
(v0.7) pkg> st Status `~/.julia/environments/v0.7/Project.toml` [6e4b80f9] BenchmarkTools v0.2.5+ #master
to
(v0.7) pkg> st Status `~/.julia/environments/v0.7/Project.toml` [6e4b80f9] BenchmarkTools v0.2.5+ #master(commit)
The text was updated successfully, but these errors were encountered:
We actually don't store the commit SHA (only the tree sha) for tracked branches. We could though.
Sorry, something went wrong.
No branches or pull requests
I think it would be useful to print a diff when a tracked branch is updated. Current behaviour:
which IMO would be better as
Additionally, perhaps we should always print the commit hash for tracked branches, e.g.
st
would change fromto
The text was updated successfully, but these errors were encountered: