Per the editor's README, "Edit directly" for an existing event opens it on github.dev over `events/.json`, while new events go through GitHub's prefilled new-file page (github.dev can't create files from a URL).
`ote.config.json` already exists in any repo that ran through the organizer kit setup — but editing it currently goes through the new-file flow instead of opening the existing file. It should behave like editing an existing event: link straight to the file, e.g.
```
https://vscode.dev/github///blob/main/ote.config.json
```
(github.dev works the same way and is what the rest of the direct-edit flow already uses — either is fine as long as it opens the existing file rather than trying to create a new one.)
Per the editor's README, "Edit directly" for an existing event opens it on github.dev over `events/.json`, while new events go through GitHub's prefilled new-file page (github.dev can't create files from a URL).
`ote.config.json` already exists in any repo that ran through the organizer kit setup — but editing it currently goes through the new-file flow instead of opening the existing file. It should behave like editing an existing event: link straight to the file, e.g.
```
https://vscode.dev/github///blob/main/ote.config.json
```
(github.dev works the same way and is what the rest of the direct-edit flow already uses — either is fine as long as it opens the existing file rather than trying to create a new one.)