For testing this you will need to make changes to both master and user branch,
This was my method:
Open tCC and select an org, repo and .tsv file.
Check all the merge/update buttons to see what they do on first print of the app.
Start making a change to the file
Check all the merge/update buttons to see what they do
Click save
Check all the merge/update buttons to see what they do
and so on..
For testing what happens when there are changes in master:
Click the compare target button in tCC which will take you to the right repo on DCS:
Then make sure you select the master branch, and start making changes to the same file you starting working at in tCC and others, you may need to refresh tCC or make new changes in tCC to trigger a new state update for the merge/update buttons.
For testing this you will need to make changes to both master and user branch, This was my method:
For testing what happens when there are changes in master:
Click the compare target button in tCC which will take you to the right repo on DCS:![tcc-merge-update-1](https://user-images.githubusercontent.com/4523496/233374160-7c1335f8-891b-45e7-9f01-04a95d828303.png)
Then make sure you select the master branch, and start making changes to the same file you starting working at in tCC and others, you may need to refresh tCC or make new changes in tCC to trigger a new state update for the merge/update buttons.