Open disruptek opened 4 years ago
If you install a duplicate tag or branch that nimph also identifies elsewise, then it may warn that it cannot meet the given requirement though it is in fact already met correctly.
I think the solution is probably to add the current branch (and a lookup of the target ref) to the list of matching oids, but I wouldn't mind some additional input here from someone with an opinion...
I haven't seen nimph do the wrong thing, exactly, but there's no reason to assume it won't break somewhere. I put a redundant tag on
cutelog
so we can monitor misbehavior.