We are using this approach for a long time. This works like a charm. For us is every start the git repository in github. So this is a must have for us.

I did add comment to a similar ticket: #12312 (comment)

This extension should work with Gitlab.com (and self-hosted), Github.com (and self-hosted) and if possible Bitbucket and Azure Devops :)

I did a POC of this and it works well, we just need to think of how to define the URL schema in the extension

ie:

`${address}/templates/${templateName}/workspace?mode=${disableAutostart ? "manual" : "auto"}&param.git_repo=${currentHref}`

Example in action

@michaelbrewer this is awesome!

cc: @BrunoQuaresma

@Tirzono, we started working on this a few weeks ago. I hope what we have planned will be helpful to you.

@michaelbrewer, this is awesome. We started following a similar path, but now we may have a "better" one... we still need to validate a few things first before sharing with you all. 👀 🤞

Would love to test this out, and help give feedback. This would reduce the setup needed per project and also allow for template conventions (open in coder) along with enhancements like "open in coder" where it can reuse an existing workspace.

Also features like "Open branch in Coder", "Open merge request in coder" can also be realiized.

Yes, we plan to support opening in any branch/merge and in pull requests. It's good to see we are aligned.

@BrunoQuaresma i have done some of the ground work to support this via terraform modules and also an issue to support merge requests etc..

• https://github.com/coder/modules/tree/main/git-clone#github-clone-with-branch-name
• rfc(git-clone): add support for pull request and merge request urls registry#67

However i would be much better for the coder agent / platform to handle this over a complicated terraform provider, as you will find some cases like gitlab you will need to perform a number of api calls to determine the branch etc.

Gitpod handles this kind of this pretty well, and i am hoping Coder can do that same natively.

Either way, i am all for dropping developing any kind of internal chrome extension in favor of an official chrome extension

Hey folks, thanks for all the great feedback here. We have an early access version of our chrome extension here: https://chromewebstore.google.com/detail/coder/ijfjglcnedpgnkfbockocdijmlhoafpm

I'm going to close out this issue in favor of #8462 so that discussion can happen in one place.