Easily find issues by searching: #<Issue ID>
Example: #1832
Easily find members by searching in: <username>, <first name> and <last name>.
Example: Search smith, will return results smith and adamsmith
| Dev |
|
| QA |
|
| Priority | Low |
| Complexity | Unknown |
| Component | App - Version Control - GIT |
| Version | 14.0 |
Problem regarding not stashing unstages/untracked changes as in ADStudio 14 Dev 10.
Assume we have a repo with a versioned file called file1.txt.
Create a new file called file2.txt without adding it to be tracked. If we go in the Repository Window and click Stash, the Stash window appears showing an extra warning message "Currently we do not support creating stash with untracked changes". Clicking now the Stash Changes button an error message would be expected to appear as there is nothing supported that can be stashed, however a new stash is created. Applying the new stash no modifications seem to happen.
Can you please clarify the expected behavior in this scenario?
For me the expected behavior would be to display an error message saying that there's nothing that can be stashed, and no new stash to be created - because even if there exists the new file file2.txt, this is not yet supported for stashing in ADS - so not considering file2.txt, there is nothing to be stashed.
This would be similar to the error message displayed when calling git stash on a repo with no local changes to save.
For me the expected behavior would be to display an error message saying that there's nothing that can be stashed, and no new stash to be created - because even if there exists the new file file2.txt, this is not yet supported for stashing in ADS - so not considering file2.txt, there is nothing to be stashed.
This would be similar to the error message displayed when calling git stash on a repo with no local changes to save.
Makes sense to me.
I will make changes to show an error message as described.
Makes sense to me.
I will make changes to show an error message as described.
I have added error message if the working copy contains only untracked file changes. Btw, I want to clarify a definition here,
The error message now ==> "You only have untracked file changes. Currently we do not support creating stash with untracked files."
To avoid any confusion between I have modified "untracked changes" to "untracked file changes". Please let me know if we need more fine tuning.
I have added error message if the working copy contains only untracked file changes. Btw, I want to clarify a definition here,
The error message now ==> "You only have untracked file changes. Currently we do not support creating stash with untracked files."
To avoid any confusion between I have modified "untracked changes" to "untracked file changes". Please let me know if we need more fine tuning.
Verified using ADStudio 14 Dev 13, behavior looks fine now.
Closed.
Verified using ADStudio 14 Dev 13, behavior looks fine now.
Closed.
Issue #8352 |
| Closed |
| Fixed |
| Resolved |
Completion |
| No due date |
| Fixed Build 31393 |
| No time estimate |
Can you please clarify the expected behavior in this scenario?