What has been activated to make these 3 files appear? (CoverageMergeHelperWorkflow.xaml, GlobalVariablesexAnAYKTq4.dll and applicationsMetadata.json)

We have started using Studio and are syncing our developments using Git.
Since last week 3 new files are showing up in one developer’s working directory, that are deleted on the working directories of the other developers after they published to Orchestrator.
If the initial developer deletes them manually they are showing up again after he is doing a publish.

The files are:
CoverageMergeHelperWorkflow.xaml
GlobalVariablesexAnAYKTq4.dll
applicationsMetadata.json

Just being curious.
What is different - in the settings - of that dev?

@heiko_wagner

Welcome to the community

can you check on the repo if those files are present

also if they are using same branch or each is using thier own branch derived from main?

cheers

Each one of our developers is using his own branch.
They came from developer 1 and were pulled into main.

Then developer 2 recognized that - after he published - they were deleted on his side.

@heiko_wagner

then please let the other developer facing this issue push the code after deleting and when you delete and push in summary you would see the changes where you can confirm if deletion is done or not

As mentioned in the branch they might be present so its syncing…removing from branch should remove locally as well

cheers

Yes, they are removed from developer 1 after he is doing a merge.
But they are created again after developer 1 is doing another publish.

It does not hurt.
Just curious what developer 1 is doing different to the others :slight_smile:

Let me add the fact that after publishing to Orchestrator we are using GitHub Desktop to sync to GitHub.
We are not using Git from within the Studio.

Update:
We found that the 3 files also appear on other developers working directory if the try to publish the scripts of developer 1.
(Normally we are all asked to set our scripts to “do not publish” before committing and doing a pull request to Git)
So I can state that the reason lies in the script.
Developer 1 is doing automation using “Use Application/Browser Chrome”