vscode-git-graph VS publish-vscode-extension

Quite a while ago, the GitLens+ plugin gained the Commit Graph feature--the same graph you see in GitKraken. Until then I had used Git Graph for visualizing my repositories and GitLens+ for git blame in the GUI. Since one plugin could now do both, the natural course of action was to remove the other--goodbye, Git Graph!

I'm a paying user of Fork, it's my favorite Git GUI, I love it.

However, it "only" supports macOS and Windows. I'm migrating to Linux for my work and home computers, so I haven't used it in a while, just so I can get familiar with other tools available on Linux - and, importantly, learning to do more advanced Git operations in the terminal.

So far I still depend on a GUI, mainly VS Code's built-in Git integration and GitGraph.

https://github.com/mhutchie/vscode-git-graph

Also looking at GitLens: https://www.gitkraken.com/gitlens

..But I sure miss using Fork. I used it everyday for the last couple years. It does everything I want to do with Git, the UI is familiar and well-designed.

I see the main developer @DanPristupov is on HN, maybe he'd consider supporting Linux? I fully understand if you don't, since creating the same application for two OSes must be quite difficult already, especially for a small team rather than a company.

Probably the most underrated software I use daily are some of my Firefox extensions.

https://github.com/einaregilsson/Redirector redirects my YouTube, Google, Twitter and Reddit links to privacy friendly frontends (i.e. Invidious, Startpage, Nitter and Libreddit).

https://github.com/proginosko/LeechBlockNG helps me staying away from time sinks on the internet during the day.

On the development side I use...

https://github.com/aaronvegh/nsregextester as my tried and true tool for regex debugging.

https://github.com/mhutchie/vscode-git-graph is a marvelous Git GUI for VSCode.

VS Code does not appear to provide a stylesheet or anything to help you get off the ground, AFAICT… I wish they did. Every extension I know of has to implement basic components from scratch, styling and all. Seems like a lot of boilerplate is necessary before you can start developing anything the user will see on screen.

I have written a number of extensions, and I use the publish-vscode-extension GitHub action to publish my extensions to both marketplaces.

Lastly we will package and publish our extension using the Visual Studio Code Extension Manager and a GitHub Action called HaaLeo/publish-vscode-extension. The advantage of having the packaging and publishing step separated is that we can attach the compiled .vsix file as an artifact to the workflow and offer it as download. Make sure to generate a token (named in the workflow as VSC_MKTP_PAT and OPEN_VSX_TOKEN) to allow GitHub to publish your extension.

I use this github action to automate publishing of an extension to both marketplaces, publication is triggered when the main branch is updated. There a couple of other github actions for