mirror of
https://codeberg.org/forgejo/forgejo
synced 2026-07-14 21:32:19 +02:00
97572bef1f
While helping @vsdl set up their development, we had to make a couple of changes to the default VSCodium configuration. I found myself having to update my own config as well because I wasn't able to run tests from VSCodium anymore. So I wonder if something changed on Forgejo or VSCodium's side that made those edits necessary in some circumstances. Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/12772 Reviewed-by: Gusted <gusted@noreply.codeberg.org> |
||
|---|---|---|
| .. | ||
| autocompletion | ||
| environment-to-ini | ||
| fhs-compliant-script | ||
| gitea-monitoring-mixin | ||
| ide | ||
| init | ||
| launchd | ||
| legal | ||
| options/label | ||
| supervisor | ||
| systemd | ||
| coverage-helper.sh | ||
| README | ||
| update_dependencies.sh | ||
| upgrade.sh | ||
All files in subdirectories are templates, do modifications based on your environment first.