Contributing

:+1:🎉 First off, thanks for taking the time to contribute! 🎉👍

Code of Conduct
Reporting Bugs
Making Changes

Code of Conduct

This project and everyone participating in it is governed by the VSCodium Code of Conduct. By participating, you are expected to uphold this code.

Use of AI

We welcome use of AI tools to help draft discussions, issues, or code, but please follow these rules:

Use AI tools responsibly and disclose their use.
Ensure all content passes a human review for authenticity and quality.
Be concise. Do not write verbose discussions, issues or PR.

Discussions, issues or PR that consist solely of unvetted AI outputs may be closed at the maintainer's discretion.

Reporting Bugs

Before Submitting an Issue

Before creating bug reports, please check existing issues and the Troubleshooting page as you might find out that you don't need to create one. When you are creating a bug report, please include as many details as possible. Fill out the required template, the information it asks for helps us resolve issues faster.

Making Changes

If you want to make changes, please read the Build page.

Building VSCodium

To build VSCodium, please follow the command found in the section Build Scripts.

Updating patches

If you want to update the existing patches, please follow the section Patch Update Process - Semi-Automated.

Add a new patch

first, you need to build VSCodium
then use the command ./dev/patch.sh <your patch name>, to initiate a new patch
when the script pauses at Press any key when the conflict have been resolved..., open vscode directory in VSCodium
run npm run watch
run ./script/code.sh
make your changes
press any key to continue the script patch.sh

2.1 KiB Raw Permalink Blame History