-
Notifications
You must be signed in to change notification settings - Fork 533
Git::Base(or Lib)#describe does not output dirty flag, even if it was requested #429
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
Comments
A friendly reminder that this issue had no activity for 60 days. |
why is this issue ignored? it takes 10 seconds to reproduce got into a git repo, make some change, compare with ruby git run
this is clearly a bug, why is this issue stale ? |
@a4z this project was in a bit of slump for the past year or so. We are just getting it going again. |
ah, OK, thanks for the information! if you need some help, no problem there is some inconsistency how parameters are taken by the function Line 117 in e0a385f
so this does not work I guess, some other parameters of this function might have some similar problem if this can wait (I guess it can) I can submit a PR the next or next next weekend, if no one else fixes it until then. |
I would really appreciate a PR that fixes this issue. The implementation should be to use symbols as the key into the arr_opts hash and not strings. You are correct that other options to arr_opts << "--abbrev=#{opts['abbrev']}" if opts[:abbrev]
arr_opts << "--candidates=#{opts['candidates']}" if opts[:candidates]
arr_opts << "--match=#{opts['match']}" if opts[:match] The I would take a fix for this to put things on the right track. However, this points out the need for better testing -- across the board. |
Signed-off-by: a4z <harald.achitz@gmail.com>
PR done, not improved tests because unsure how to do it ,but I might look into it next time I find some time |
Subject of the issue
using ruby git like this
output:
v0.0.0-2-g03626ae
but running git directly produces the correct result
output:
v0.0.0-2-g03626ae-dirty
Your environment
Steps to reproduce
Generate a dirty repo, add a tag, add a commit, change a file,
now you have a dirty repo
run
Expected behaviour
there should be a dirty in the output string (at the end)
Actual behaviour
the dirty flag is not in the output
The text was updated successfully, but these errors were encountered: