This is a popular feature with Coder v1 customers.

Why?

Devs are familiar with their Git provider as part of their daily flow. So they can jump to Coder directly from a repo they need to work on. (which takes you to a proper template)

Spoke to @kylecarbs and @bpmct offline about this. We're going to go the simple route for now. Ben can share more.

TLDR is we're going to simply provide a button for now and evaluate pre-filled params down the road.

This issue is becoming stale. In order to keep the tracker readable and actionable, I'm going close to this issue in 7 days if there isn't more activity.

I'am really looking forward for this feature

Also consider a "personalize" step

How this will work (still subject to change, however):

1. A template admin edits the template to specify what repo(s) it is compatible with (or regex-like https://github.com/*, https://gitlab.company.com/myorg/*).
2. A template admin can embed an "Open in Coder" button on their repo or internal wiki
3. When a user clicks the button in the repo, they can pick a compatible template and then create/use an existing workspace
4. The workspace will attempt to clone the repo, with logic editable via the Coder agent's startup script. If the user has not linked their git provider yet, Coder will ask them to connect before they can enter their workspace.

Users can also create a workspace from a repo via the Coder dashboard:

Down the road, Coder may have first-class support for devcontainers #5559. If the repo contains a devcontainer, Coder would be able to spin it up and launch the agent inside the container.

https://gitlab.com/gitlab-org/gitlab/-/issues/384217

Would it be possible to contribute this to GitLab so that users may use Coder without adding the button in the markdown file?