GitHub repo wasn't listed in autodeploy dropdown menu

[jschuur]

I just tried to set up auto-deployment, and the repo dropdown list didn't show a newer repo that I created a few days ago, despite having given access to all repos (I think).

It still didn't show up after I toggled the GitHub integration off and on again (and gave access again on the GitHub site).

The only way I got the new repo to show was to delete the whole console GitHub app and have that reinstall when I turned the GitHub integration on again on the SST console site.

I validated this again by creating another new repo now and it didn't show up when I tried to link it to an existing console app.

[kylebrague]

Hi everyone,

We’ve encountered this issue frequently. After reviewing the source code, we discovered a workaround to force a GitHub repo sync. SST team, please let me know if this approach has unintended side effects or if there’s a better alternative.

---

Trigger the sync by calling this endpoint (via curl or your browser):

curl --location 'https://backend.console.sst.dev/github/installed?state={workspaceID}&installation_id={installationID}'

• workspaceID

  • Retrieve it from the GET https://backend.console.sst.dev/account response in the Console (check the Network tab in DevTools).
  • The JSON payload includes an array of workspaces.
  • You can also call this endpoint directly with a valid auth token.

• installationID

  • Find it in your organization’s GitHub App settings.

  • Go to:

    https://github.com/organizations/{your-org}/settings/installations
    

  • Click on 'Configure' next to the SST app. The new URL will look like this:

    https://github.com/organizations/{your-org}/settings/installations/{installationID}
    

  • Copy the number at the end of the URL.

---

Hopefully this can be useful for others. Thanks!