- Notifications
You must be signed in to change notification settings - Fork16
PermalinkChoose a base ref {{ refName }}default Choose a head ref {{ refName }}default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also orlearn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also.Learn more about diff comparisons here.
base repository:coder/jetbrains-coder
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
Uh oh!
There was an error while loading.Please reload this page.
base:v2.22.3
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}defaultLoading
...
head repository:coder/jetbrains-coder
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
Uh oh!
There was an error while loading.Please reload this page.
compare:main
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}defaultLoading
- 5commits
- 16files changed
- 4contributors
Commits on Sep 22, 2025
Changelog update -
v2.22.3
(#580)* Changelog update - v2.22.3* chore: trigger CI build---------Co-authored-by: GitHub Action <action@github.com>Co-authored-by: Faur Ioan-Aurel <fioan89@gmail.com>
Commits on Sep 29, 2025
* Update README.mdadded note to recommend the Toolbox plugin* Update README.mdAdded link to docs
Commits on Oct 1, 2025
impl: prefer agent name over agent id in URI handler (#585)
* impl: prefer agent name over agent id in URI handlerAgent name is easier to resolve in jetbrains gateway module* impl: prefer agent name over agent id in URI handler (2)Error reporting should also prefer agent name over the agent id.* chore: update and fix UTsTest cases related to agent matching have to be updatednow that agent name is preferred over agent id.* chore: refactor UTs related to agent matching in URI handlingRewrote the entire test to be easier to read and debug.
impl: add the option to disable ssh wildcard configuration (#584)
* impl: add the option to disable ssh wildcard configurationIt will be used later by the Coder Settings view to allow usersto enable or disable SSH hostname wildcard configuration.* impl: expose ssh wildcard config in the Settings pageUpdated the UI component to allow configuration by the user* impl: take into account wildcard configurationwhen generating the ssh config for Coder Gateway.Up until now we just checked if the Coder deployment supportsthis feature, but now users have to option to continue touse expanded hostnames in the ssh config.* fix: force CLI manager to use user settingsCLIManager can be created with default settings (simplifies testing),among which the ssh wildcard config is enabled. But in reality theconfig can be disabled by the user.* impl: ability to start a recent workspace connection after ssh wildcard config was changedCurrently, if a user starts a connection with wildcard enabled and then later on it disablesthe wildcard config then the recent connections becomes unusable because the hostnames are invalid.The issue can reproduce the other way around as well (start with wildcard ssh config disabled,start an IDE and then later on enable wildcard config)This commit addresses the issue by resolving the hostname on demand when the user wants toopen the remote IDE from the recent connections panel.* chore: update README* chore: next version is 2.23.0* fix: don't show twice the connection to the same workspaceConnections started with two different hostnames (because of the ssh wildcard config)can be rendered twice in the Recent projects panel.With this commit we ignore the hostname and instead use the workspace name and deployment URL.
Commits on Oct 2, 2025
Changelog update -
v2.23.0
(#586)* Changelog update - v2.23.0* chore: for build trigger---------Co-authored-by: GitHub Action <action@github.com>Co-authored-by: Faur Ioan-Aurel <fioan89@gmail.com>
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:git diff v2.22.3...main
Uh oh!
There was an error while loading.Please reload this page.