4 ms·

IntelliJ's .idea/ folder has its own .gitignore and Copilot expects to find things committed under a .github/ folder. I used to be a purist about IDE configura

IntelliJ's .idea/ folder has its own .gitignore and Copilot expects to find things committed under a .github/ folder. I used to be a purist about IDE configurations, but if everyone isn't on the same page about formatting and stuff like that you see a lot of file churn as things move around. I would have said the same thing about the .github/ folder, but I've had to add things to it to prevent Copilot from thinking bad patterns in existing code are actually good patterns that should be repeated. It makes more sense when your communication between teammates is constrained to the repository, because your other communication channels are already saturated. They're meta concerns that really have nowhere to go outside the repository without getting lost.

cosmotic 5mo ago
.idea was designed to be added to source control. It doesnt have to be, but everyone on the team using the same project configuration has its advantages. Code style can be checked in too, reducing or preventing the churn you speak of.
larusso 5mo ago
Other GitHub metadata goes into the .github folder as well. And that is expected to be commuted. Like action workflows/actions and CodeOwners Pull and issue templates etc.
CivBase 5mo ago
> but if everyone isn't on the same page about formatting and stuff like that you see a lot of file churn as things move around. IMO that is what automated static analysis jobs are for. Let me configure my IDE how I want.
- theshrike79 5mo ago
  [dead]