Closed arunoruto closed 1 week ago
Hey @arunoruto, that's great! I've sent you an invite to the tinted-theming github org team @tinted-theming/vivid which will have maintainer access to the repo. To transfer the repo, join the org and go to the repo settings. At the bottom of the page there should be a transfer button. Let me know if you run into any issues :)
Ok Great :) Since you're now in the org you should just be able to create a new repo, so no more hoops. Once the zed repo (or any future template repo you work on) is in a good state, let me know and I'll create a github team to be the maintainer of the repo and add a github action + repo secret to enable weekly builds.
Sorry for posing in an already closed issue, but I am not sure how to contact you otherwise.
I had some free time, and created the zed theming schema (using a bit of chatgpt to aid me), and cleaned up the vivid repo. The only thing left, would be to replace the secrets.GITHUB_TOKEN
with secrets.BOT_ACCESS_TOKEN
.
Also, I had some difficulties with the go builder action, and replaced it with the rust version, which works fine now!
I am also planning on creating a zed extension, so everyone can quickly install the zed themes :)
Great job @arunoruto on creating the template and setting it all up!
I've added the BOT_ACCESS_TOKEN
secret to base16-vivid. Right now you're able to commit the theme updates without that secret because there isn't write protection on the main
branch. It's not necessary to have write protection on while doing active development, but when things are stable it's generally good to add it so other maintainers are required to create PRs and getting the others' approval before making a change. However, it's not strictly necessary if it becomes a hurdle for maintainers.
I've just created a new shared action in tinted-theming/home: https://github.com/tinted-theming/home/blob/main/.github/workflows/shared-build-template-and-commit-themes.yml - This should remove some boilerplate for template maintainers. I'll create a PR updating your local action.
There are several people on the tinted-theming matrix chat group: https://matrix.to/#/#tinted-theming:matrix.org
Hi! I came across base16 through using stylix to manage my color scheme on my PC. To also apply a color scheme to an
ls
command, like eza or lsd, theLS_COLORS
variable has to be set. That setting is quite cumbersome, so I am using vivid to make it easier! With this project, more themes can be generated for vivid! One can put the content of thethemes
folder into$HOME/.config/vivid/themes
and preview or use any of them!If I am missing anything, please hit me up!