You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Add support for --workspace flag
Signed-off-by: lelia <lelia@socket.dev>
* Add tests to cover new workspace CLI args
Signed-off-by: lelia <lelia@socket.dev>
* Update README to document new CLI flag, and differentiate it from existing workspace-name flag
Signed-off-by: lelia <lelia@socket.dev>
* Update refs to use generic project names
Signed-off-by: lelia <lelia@socket.dev>
* Bump CLI version
Signed-off-by: lelia <lelia@socket.dev>
* Pin python and virtualenv versions to unblock builds
Signed-off-by: lelia <lelia@socket.dev>
* Bump published SDK version refs
Signed-off-by: lelia <lelia@socket.dev>
* Tweak helper text for CLI flag
Signed-off-by: lelia <lelia@socket.dev>
* Update CODEOWNERS to reflect proper team structure
Signed-off-by: lelia <lelia@socket.dev>
* Increment version again for release
Signed-off-by: lelia <lelia@socket.dev>
---------
Signed-off-by: lelia <lelia@socket.dev>
Copy file name to clipboardExpand all lines: README.md
+18-9Lines changed: 18 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -43,6 +43,8 @@ These examples are production-ready and include best practices for each platform
43
43
44
44
## Monorepo Workspace Support
45
45
46
+
> **Note:** If you're looking to associate a scan with a named Socket workspace (e.g. because your repo is identified as `org/repo`), see the [`--workspace` flag](#repository) instead. The `--workspace-name` flag described in this section is an unrelated monorepo feature.
47
+
46
48
The Socket CLI supports scanning specific workspaces within monorepo structures while preserving git context from the repository root. This is useful for organizations that maintain multiple applications or services in a single repository.
47
49
48
50
### Key Features
@@ -114,7 +116,7 @@ This will simultaneously generate:
| --repo | False | *auto* | Repository name in owner/repo format (auto-detected from git remote) |
146
+
| --workspace | False | | The Socket workspace to associate the scan with (e.g. `my-org` in `my-org/my-repo`). See note below. |
147
+
| --repo-is-public | False | False | If set, flags a new repository creation as public. Defaults to false. |
148
+
| --integration | False | api | Integration type (api, github, gitlab, azure, bitbucket) |
149
+
| --owner | False | | Name of the integration owner, defaults to the socket organization slug |
150
+
| --branch | False | *auto* | Branch name (auto-detected from git) |
151
+
| --committers | False | *auto* | Committer(s) to filter by (auto-detected from git commit) |
152
+
153
+
> **`--workspace` vs `--workspace-name`** — these are two distinct flags for different purposes:
154
+
>
155
+
> - **`--workspace <string>`** maps to the Socket API's `workspace` query parameter on `CreateOrgFullScan`. Use it when your repository belongs to a named Socket workspace (e.g. an org with multiple workspace groups). Example: `--repo my-repo --workspace my-org`. Without this flag, scans are created without workspace context and may not appear under the correct workspace in the Socket dashboard.
156
+
>
157
+
> - **`--workspace-name <string>`** is a monorepo feature. It appends a suffix to the repository slug to create a unique name in Socket (e.g. `my-repo-frontend`). It must always be paired with `--sub-path` and has nothing to do with the API `workspace` field. See [Monorepo Workspace Support](#monorepo-workspace-support) below.
0 commit comments