Accidentally checked-in file
What is the recommended procedure when you accidentally checked-in a file to a change-set?
Assume that the changes in the file are intended, but the changed file should be checked-in to a different change set.
Using Undo will remove the file from the change set, but it as well reverts the changes to the local file, what is not intended in this scenario.
I help myself by making a local copy of the file, perform Undo, and then replace the local file with the copy. Is this the intended procedure or does RTC provide actions to achieve the same goal?
Assume that the changes in the file are intended, but the changed file should be checked-in to a different change set.
Using Undo will remove the file from the change set, but it as well reverts the changes to the local file, what is not intended in this scenario.
I help myself by making a local copy of the file, perform Undo, and then replace the local file with the copy. Is this the intended procedure or does RTC provide actions to achieve the same goal?
3 answers
You can right-click on the file in the change set and move it to a new change set or another change set.
What is the recommended procedure when you accidentally checked-in a file to a change-set?
Assume that the changes in the file are intended, but the changed file should be checked-in to a different change set.
Using Undo will remove the file from the change set, but it as well reverts the changes to the local file, what is not intended in this scenario.
I help myself by making a local copy of the file, perform Undo, and then replace the local file with the copy. Is this the intended procedure or does RTC provide actions to achieve the same goal?
Unfortunately, you cannot directly undo the change to make it go back to an unresolved status. If you wanted something like that, I would suggest creating a patch and selecting the one change to be in the patch. When the patch is applied and merged into your workspace, you'll have the change as unresolved again.
Although, it's extra work for when something will eventually be checked-in. It's perfectly OK to keep it checked-in because the checked-in change only exists in your repository workspace until it is delivered somewhere else. There is no harm from accidentally checking-in a change unless your team has a process of only checking-in changes that will be immediately delivered.
Although, it's extra work for when something will eventually be checked-in. It's perfectly OK to keep it checked-in because the checked-in change only exists in your repository workspace until it is delivered somewhere else. There is no harm from accidentally checking-in a change unless your team has a process of only checking-in changes that will be immediately delivered.
Thank you!
I was looking for a method to undo the check-in action.
Moving the change to a different/new change set doesn't bring the file back to Unresolved status, but that's not the point.
Thank you for helping me to change my way of thinking.