-
Notifications
You must be signed in to change notification settings - Fork 2.1k
fix(forge
): sync branch with remote on update
#11401
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
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
makes sense. left a comment, optionally to add it here but I think it's really useful - that is use git log -1 --oneline
to show rev that you updated to
assert!(git.head().unwrap() == forge_std.rev(), "Forge std should be at the release tag"); | ||
|
||
let expected_output = format!( | ||
r#"Updated dep at 'lib/forge-std', (from: tag={}@{}, to: branch=master@{}) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think could be really nice and useful to call git log -1 --oneline
for showing the new commit / comment that you updated to
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We are displaying the rev
it updated to after the @
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah, but git log -1 --oneline displays more details, as for example
8bbcf6e (HEAD, tag: v1.10.0) feat: release 1.10.0 (#701)
Motivation
Currently,
forge update owner/repo@branch
doesn't work correctly, as it fails to sync the branch with the remote and only updates it to the latest local commit of that branch.Solution
PR Checklist