Update github extension

[workeffortwaste]

Description

Adds a 'Clone in GitHub Desktop' action to the repository actions, with a Cmd+Shift+G shortcut, which opens the selected repository in the in the GitHub Desktop app ready for cloning.

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 @aeither @marcotf @qeude @nesl247 @xilopaint @antonengelhardt @bangerang @wottpal @LitoMore @d-mitrofanov-v @j3lte @jfkisafk @vlasischar @JavaLangRuntimeException @shyakadavis @sushichan044 @luarmr @nicolas-marien @ionTea @ridemountainpig @kud @MartinGonzalez @brandonnly @oscmarb @emergerrrd @ryo246912 @gfazioli @wonbywondev @SandeepBaskaran 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.

📋 Quick checkout commands

BRANCH="ext/github"
FORK_URL="https://github.com/workeffortwaste/raycast-extensions.git"
EXTENSION_NAME="github"
REPO_NAME="raycast-extensions"

git clone -n --depth=1 --filter=tree:0 -b $BRANCH $FORK_URL
cd $REPO_NAME
git sparse-checkout set --no-cone "extensions/$EXTENSION_NAME"
git checkout
cd "extensions/$EXTENSION_NAME"
npm install && npm run dev

We're currently experiencing a high volume of incoming requests. As a result, the initial review may take up to 15 business days.

[greptile-apps]

Greptile Summary

Adds a repository action that opens the selected GitHub repository in GitHub Desktop and documents the feature in the changelog.

• Adds a “Clone in GitHub Desktop” action with a keyboard shortcut.
• Records the selected repository in visit history when the action opens.
• Adds a merge-dated changelog entry for the feature.

Confidence Score: 4/5

The PR appears safe to merge, with a non-blocking action-ordering issue that should be corrected to preserve existing navigation positions.

The clone URL construction matches the repository URL shape and no runtime failure was established, but the new action shifts existing action-panel entries instead of preserving their order.

Files Needing Attention: extensions/github/src/components/RepositoryActions.tsx

Important Files Changed

Filename	Overview
extensions/github/src/components/RepositoryActions.tsx	Adds the GitHub Desktop clone action, but inserts it before existing actions rather than appending it as required.
extensions/github/CHANGELOG.md	Adds a correctly positioned changelog entry using the required merge-date placeholder.

Prompt To Fix All With AI

### Issue 1
extensions/github/src/components/RepositoryActions.tsx:148-154
**Preserve existing action ordering**

Inserting this action before the existing star toggle shifts that action and all following entries from their established positions, disrupting position-based navigation and muscle memory. Append the new action after the existing actions to preserve their order.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

_{Reviews (1): Last reviewed commit: "Update github extension" | Re-trigger Greptile}

[greptile-apps]

Preserve existing action ordering

Inserting this action before the existing star toggle shifts that action and all following entries from their established positions, disrupting position-based navigation and muscle memory. Append the new action after the existing actions to preserve their order.

Rule Used: What: New action panel actions should be appended ... (source)

Prompt To Fix With AI

This is a comment left during a code review.
Path: extensions/github/src/components/RepositoryActions.tsx
Line: 148-154

Comment:
**Preserve existing action ordering**

Inserting this action before the existing star toggle shifts that action and all following entries from their established positions, disrupting position-based navigation and muscle memory. Append the new action after the existing actions to preserve their order.

**Rule Used:** What: New action panel actions should be appended ... ([source](https://app.greptile.com/raycast/-/custom-context?memory=cde63d3f-214c-4294-9a2a-bb8323ef7d33))

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!