Add a select few ai settings folders to gitignore

[Duncan-Brain]

Description

Adds a select few ai setting to the gitignore folder.

There are many more but these are the ones we discussed adding.

Jira link:

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• Passes test case
• UI components visually reviewed on desktop view
• UI components visually reviewed on mobile view
• Other (please explain)

Checklist:

• I have commented my code, particularly in hard-to-understand areas
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• The precommit and linting ran successfully
• I have added or updated language tags for text that's part of the UI
• I have ordered translation keys alphabetically (optional: run pnpm i18n to help with this)
• I have added the GNU General Public License to all new files

[SayakaOno]

Thank you Duncan!
@kathyavini Would you be able to check this? I haven’t had these files generated on my end yet 🙏

[kathyavini]

Works from the Claude end! @Duncan-Brain do you know how you came to decide on the .copilot folder though? I think the current GitHub copilot docs reference files under .github (.github/instructions and .github/prompts etc.) so just want to make sure that .copilot folder is an existing convention as well; not seeing it in the docs.

[kathyavini]

Did your copilot generate a .copilot folder at some point? Or did you create one manually? I think the official convention is now always nesting under .github/, i.e. .github/copilot-instructions.md and .github/instructions/ (based on this GitHub documentation).

I don't use repo-level instructions like that, but I did end up with a .github/prompts/ as well from using the VS Code planning mode so maybe that could be added too?

[Duncan-Brain]

This is what we discussed, it was not generated, I saw it under other filenames as well.. we seemed to choose this on call!

Edit: I personally had mine under .github at time we discussed. But we do put a lot of actually useful stuff in there that the suggestion on call to use a copilot was fine

[kathyavini]

I thought we left the conversation saying we would nest CLAUDE.md under .claude/ so we only need to .gitignore .claude/ (or at least, I moved my CLAUDE.md file subsequent to that tech daily convo 😂). The root level CLAUDE.md might make more sense if we ever wanted to share / commit one to repo.

It works from either place though so this is also good; we can always un-ignore at the point of sharing if we decide we want to do that.

[Duncan-Brain]

Agreed but I thought we were doing both based on convo last time -- can edit as things change... this is a starting point