Skip to content

fix: specify --header-command when running coder start #526

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Jun 5, 2025
Merged

fix: specify --header-command when running coder start #526

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
2f9f989
fix: specify `--header-command` when running `coder start`
aslilac Jun 2, 2025
a024e2d
Merge branch 'main' into lilac/specify-header-command
aslilac Jun 2, 2025
ddcedb7
update changelog
aslilac Jun 3, 2025
384cb15
whoops
aslilac Jun 3, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
whoops
  • Loading branch information
@aslilac
aslilac committed Jun 3, 2025
commit 384cb15abd249ccf71009bb9a4926ecf5d5614fe
5 changes: 4 additions & 1 deletion CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,10 @@

## Unreleased

### Fixed

- Use `--header-command` properly when starting a workspace.

## [v1.9.1](https://github.com/coder/vscode-coder/releases/tag/v1.9.1) 2025-05-27

### Fixed
Expand All @@ -12,7 +16,6 @@
- Multiple open instances of the extension could potentially clobber writes to
`~/.ssh/config`. Updates to this file are now atomic.
- Add support for `anysphere.remote-ssh` Remote SSH extension.
- Use `--header-command` properly when starting a workspace.

## [v1.9.0](https://github.com/coder/vscode-coder/releases/tag/v1.9.0) 2025-05-15

Expand Down