Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Doing a full revert does not update the status of "Mark for Add" files #97

Closed
MekuCube opened this issue Apr 12, 2019 · 0 comments
Closed

Doing a full revert does not update the status of "Mark for Add" files #97

MekuCube opened this issue Apr 12, 2019 · 0 comments
Assignees
@SRombauts
Labels
bug

Comments

@MekuCube
Copy link
Contributor

MekuCube commented Apr 12, 2019 •
edited
Loading

"Mark for Add" files do not have their status updated after a full revert (Source Control -> Revert)

Steps to replicate:

  • Add a new asset
  • Mark the asset with Right-click -> Source Control -> Mark for Add
  • Perform a full revert via Source Control -> Revert
  • Notice that the status of the asset is not updated to reflect the revert (incorrect behavior)
  • Run Source Control -> Refresh. Notice that the status of the asset is now correctly updated.
MekuCube added a commit to MekuCube/UE4GitPlugin that referenced this issue Apr 12, 2019
@MekuCube
Fixed a bug where "Mark for Add" files did not have their status upda…
671286c 
…ted after a full revert.

Steps to replicate:
* Add a new asset
* Mark the asset with Right-click -> Source Control -> Mark for Add
* Perform a full revert via Source Control -> Revert
* Notice that the status of the asset is not updated to reflect the revert.

Related issue: SRombauts#97
@MekuCube MekuCube mentioned this issue Apr 12, 2019
Merged
@SRombauts SRombauts self-assigned this May 2, 2019
@SRombauts SRombauts added the bug label May 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@SRombauts SRombauts

Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@SRombauts @MekuCube