api-playground VS dev

GitLab team member here.

Maybe you can re-use the script I shared in this comment [0] to query the GitLab REST API to generate an index. I'm a fan of using the API programmatically, and tend to avoid git checkout/grep/etc. inside CI/CD pipelines (works too, everyone is free to choose their way).

Yet again, I love API challenges, so I've created a new script which parses a defined markdown footer for Tags and Due date, and generates an ordered index by due date. I did not know which format you are using, so I made up my own, see the MR description [1] and docs [2].

The script lives in [3] and is a mix of fetching files, parsing content with regex, and generating the index + creating a commit to upload automatically.

A demo overview is shown in [4] with the generated index.md, ordered by due date and linking the files by parsed heading title, file paths, and tags.

Hope it helps, feel free to repurpose, or ping me for questions on the GitLab community forum [5]. My Python code is a little rusty, I am slowly adopting all the 3.x design patterns after many years with 2.x.

I might follow your idea with notes and custom footer parsing. That's a really nifty idea, and helps solve my own chaos :-)

[0] https://news.ycombinator.com/item?id=32155848

[1] https://gitlab.com/dnsmichi/api-playground/-/merge_requests/...

[2] https://gitlab.com/dnsmichi/api-playground/-/tree/main/pytho...

[3] https://gitlab.com/dnsmichi/api-playground/-/tree/main/pytho...

[4] https://gitlab.com/dnsmichi/api-playground/-/tree/main/demo/...

[5] https://forum.gitlab.com/u/dnsmichi/summary

They aren't using code spaces or github.dev I believe. They are actually using "Edit in place" which is adjacent to those options. The first image in this link might help:

You are mostly right, but the "remote" aspect comes from the fact that https://github.dev/ can open any random repository (e.g. go to this LLVM README file and then hit the "github.dev" in the dropdown menu for edit). Nothing gets downloaded to your computer and happens on the cloud. You are editing a remote repository on a remote computer.

You should know with great power comes with greater bill. You can use https://github.dev/github/dev, vscode.dev, github1s.com to WRITE and READ source code, but can't compile nor run. If you want to run, you will need Github Codespace which costs money.

Checkout "github.dev" (which is based on vscode.dev)

last week i stumbled across vscode.dev and github.dev which are web versions of my beloved editor. Of course there is no terminal available, which made me curious? is ther a way or service that lets you use a linux container to remote into and use vscode on the go?

TIP: If your source code is on GitHub, and you just need to show the source code, you can use github.dev, a lightweight, browser-based editor (based on VSCode) you can access by replacing .com with .dev when typing the repository URL. It even supports some extensions such as the brilliant CodeTour, which is great for showing code in a guided way throughout your session.

I am using codespaces (github.dev) as the IDE.

I can't believe I am just finding out about https://github.dev a vscode interface for any github repo. For example: https://github.dev/expo/expo/

Add a custom search engine in Chrome and you got yourself a quick shortcut to opening any repo in github dev. In the past I would clone repo then open with vs code to monkey around. Now its CMD+L , 'gd expo/expo' to open https://github.dev/expo/expo/

Instructions for adding custom omniBar search shortcuts: https://zapier.com/blog/add-search-engine-to-chrome/

Just in case this isn't common knowledge: You can hit the period (.) key while on any github page to launch a vscode in browser (uses https://github.dev/).