It seems that the integration with GitHub generated another copy (was two now is tree) of strings.xml resource. I am not sure why this is happening, is there a way to remove the duplicates without loosing information? Also I don’t quite know which is the correct one to keep.
The repo is GitHub - TeamAmaze/AmazeFileManager: Material design file manager for Android but the other resources might have been created during a previous unlinking and relinking of the integration (as opposed to branch changes). In any case, we do use multiple branches to keep track of code for releases, will this be a problem?
Also, currently, checking against the time in the logs, it seems to only be pulling after the PR is merged (which is correct), and not creating a new resource for each PR.
My current theory is that the duplicates were caused by old integrations and should be removed. My question is how to remove them without losing information.
(The “strings.xml” one has a last update that is recent because I wanted to test if the strings.xml file was correct of a more recent version, but the last auto-update of that resource was pretty old).
Translations are stored in the TM, if the entries were used by another resource then this information will not be deleted.
As the resource are not part of any available repository you shouldn’t lose any information, but, just in case you can create a backup of your TM by heading to your project settings.
Once you have this backup you can delete the resources from your project by selecting them. You can take a look at the date to see what of them were recently used and use this criteria to delete them