You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
git diff is used to determine whether there are any changes. git diff is empty if only new, untracked files are added. This halts the migration process and asks the user for input.
I suggest one of the following solutions:
Use git status instead of git diff.
Use git add -A, then git diff --cached, i.e. stage earlier.
The text was updated successfully, but these errors were encountered:
Thanks for reaching out for this! :)
In fact we use git status in some context (handling ignores) already.
Im cant exactly remember why we have choosen git diff instead of git status, but I think I didnt want to have any accidently .jazz folders added.
I will keep this open and make some tests with it. Could probably take some time (since I dont have much free time nor a testing workspace).
diff has the nice property of a changing exit code depending on whether there are changes or not. status doesn't have that I believe, so is harder to work with.
I tried out option 2 and found no problems migrating a ~400 change set repo. If you want I can make a pull request.
git diff
is used to determine whether there are any changes.git diff
is empty if only new, untracked files are added. This halts the migration process and asks the user for input.I suggest one of the following solutions:
git status
instead ofgit diff
.git add -A
, thengit diff --cached
, i.e. stage earlier.The text was updated successfully, but these errors were encountered: