src-cli icon indicating copy to clipboard operation
src-cli copied to clipboard

Sourcegraph CLI

Results 98 src-cli issues
Sort by recently updated
recently updated
newest added

Hi. Loving using `src` from the cli so far. One small improvement I'd love to see... Is it possible for you to provide a way to customise which git diff...

``` > src ext get felixfbecker/lang-typescript GraphQL errors: [ { "locations": [ { "column": 9, "line": 25 } ], "message": "Cannot query field \"title\" on type \"ExtensionManifest\"." } ] ```

I just tried to publish an extension and just got an unhelpful JSON dump of a GraphQL error: ``` GraphQL errors: [ { "message": "registry extension publisher not found: [name...

This issue is about printing out error messages that are more nicely formatted, not about fixing any specific error message. See https://github.com/sourcegraph/src-cli/issues/20 for context.

For a correctly configured extension, `src ext publish` succeeds, but `src ext delete` does not. The error returned is: ``` GraphQL errors: [ { "message": "invalid graphql.ID", "path": [ "extensionRegistry",...

It would be nice to automate the process of creating an access token and saving it to the src-config.json file, like how `gcloud login` works. cc @ryan-blunden @attfarhan this came...

enhancement

Extension publishers should be able to set the extension as WIP by passing a flag through the CLI, without having to mention it in the extension name

The goal is to get as many extensions as possible with a `repository` object set in their package.json with the assumption that a legitimate extension will have a git repository....

Running the following command: ``` echo 'query DependencyReferences($repoPath: String!, $commitID: String!, $filePath: String!, $mode: String!, $line: Int!, $character: Int!) { repository(uri: $repoPath) { commit(rev: $commitID) { file(path: $filePath) { dependencyReferences(Language:...

https://github.com/sourcegraph/src-cli/blob/4e548d9ca9a9a4316bf4692773f44bd19f5386dc/cmd/src/extensions_publish.go#L174 The expected behaviour here would be what npm does, which is using `cmd` on Windows. This decision is automatically made by Node `child_process.exec()`. https://github.com/sourcegraph/src-cli/blob/4e548d9ca9a9a4316bf4692773f44bd19f5386dc/cmd/src/extensions_publish.go#L175 Windows uses `;` to separate...