Update github extension

[nicolas-marien]

Description

Add a preference to exclude repositories from the "my-issues-*" commands. I wanted to remove some visual cues when I am tagged by mistake on repositories I no longer contribute to.

Screencast

https://youtu.be/tZRXF2U4aao

Checklist

• I read the extension guidelines
• I read the documentation about publishing
• I ran npm run build and tested this distribution build in Raycast
• I checked that files in the assets folder are used by the extension itself
• I checked that assets used by the README are placed outside of the metadata folder

[raycastbot]

Thank you for your contribution! 🎉

🔔 @thomaslombart @unnamedd @tonka3000 @khasbilegt @pernielsentikaer @loxygenK @oilbeater @LunaticMuch @aeorge @daquinoaldo @peppy @aeither @marcotf @qeude @nesl247 @xilopaint @antonengelhardt @bangerang @wottpal @LitoMore @d-mitrofanov-v @j3lte @jfkisafk @vlasischar @JavaLangRuntimeException @shyakadavis @sushichan044 you might want to have a look.

You can use this guide to learn how to check out the Pull Request locally in order to test it.

Due to our current reduced availability, the initial review may take up to 10-15 business days

[greptile-apps]

PR Summary

Added a repository exclusion feature to GitHub extension, allowing users to filter out specific repositories from "my-issues" commands via a new preference.

• Added excludedRepositories preference to both my-issues and my-issues-menu commands in package.json
• Implemented repository filtering in useMyIssues.ts by converting comma-separated list into query exclusions
• Updated my-issues-menu.tsx and my-issues.tsx to pass the new preference to the hook
• Added changelog entry with proper {PR_MERGE_DATE} placeholder at the top of CHANGELOG.md
• Feature helps users remove visual noise from repositories they no longer contribute to but are still tagged in

_{💡 (5/5) You can turn off certain types of comments like style here!}

_{5 file(s) reviewed, 2 comment(s)
Edit PR Review Bot Settings | Greptile}