Is anybody else having troubles with new git-aggregator in 16.0 and 17.0? #593
Unanswered
ap-wtioit
asked this question in
Doodba - The image
Replies: 2 comments
-
I haven't seen this with git-aggregator, but I've seen it with mrchef, which is similar. Also I've had some cases of git checkout errors, but I've somehow fixed them all and moved on, since they weren't clearly reproducible. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Not experimenting it, but my development flow doesn't involve doing |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
This not yet a reproducable (with public commits) issue but we are seeing this on more and more systems and today it also started affecting our dev systems.
After checking out a repo with doodba 16.0 / doodba 17.0 working with it and refreshing it with setup devel on the next day we get messages like this:
Only solution that helps here is to delete the whole repo (not good if developer has local branches that are not pushed yet) and check out again.
Is this an issue that only our version has or is somebody else affected?
Beta Was this translation helpful? Give feedback.
All reactions