On my iMac when using Xcode 13. the issue seems to be linked to the simulator used by the SwiftUI preview canvas. When it first loads, it will peg the simulator at around 200% CPU usage and increase watt usage from around 60W to over 100W even after I pause and close the canvas. Only way to clear it seems to be either killing the simulator process or Xcode. If I just compile to a simulator device every time I want to check the UI changes without ever opening the canvas after Xcode starts, other than a short spike during compile, it will hover around 60W. a bit of a pain but a workaround while Apple sort out the issue.

I've figured out the issue but have not found a practical solution yet. Source control options work for projects located inside my home directory. All my projects are in a root /Data folder. If I create a symbolic link inside the /Data folder to a test project on the desktop works as expected. If I move the project inside the /Data folder, it does not work with all the options disabled except Clone and New Repository. Moving all the projects to the home folder is not an option. Xcode can read/write fine to the /Data folder. I've created a new folder in /Data2 and moved the test project to it, but the issue persists so it seems anything not in the home folder will have the source control options disabled. Works fine on my MBP and Mac mini.

Same issue with Xcode 13. I've created a brand new project and initialised local git during creation. Once created the source control options remain greyed out except for Clone and New Git Repository. When I try to add new repository it says that one already exists but still the options are disabled.