📑 Table of Contents

• Contributing to Carch

  • Understand the Codebase
  • Steps to Contribute

• Contributing to Carch Docs

• Guidelines

Contributing to Carch

We're excited that you're interested in contributing to Carch! Contributions of all kinds are welcome, whether you're fixing bugs, adding new features, or improving documentation. Follow this guide to get started.

WARNING

Before making any contributions, first open an issue in the Feature Request section. We will discuss the changes there before proceeding with implementation.

📌 Understand the Codebase

NOTE

Before contributing, understand the structure of Carch:

• The main Rust files of Carch are located in: src

src/
├── ui/
│   ├── app.rs
│   ├── mod.rs
│   ├── popups.rs
│   └── render.rs 
├── main.rs 
├── commands.rs
├── display.rs
├── script_list.rs 
└── version.rs

• All modules scripts are organized by category in:

modules/
├── Browser/     # Browser related scripts 
├── Desktop/     # Desktop environment related scripts
├── Development/ # Development tools scripts
├── System/      # System configuration scripts
└── Terminal/    # Terminal setup scripts

IMPORTANT

First, analyze how the script works before making any changes. If you want to improve or add to the project, make sure you understand the structure and how each piece interacts. This will help you contribute in a way that is consistent with the project's design.

For committing, use labels like
feat: your-commit-message or fix: your-commit-message.

Btw, before committing, if you are changing any .sh or bash script file, make sure to check the scripts/ directory and run ./check.sh for any extra white or blank spaces. If it fails, run ./cleanup.sh. That is only for bash scripts.
For Rust file changes, make sure to run cargo fmt --all --check. If there are any suggestions, run cargo fmt --all.
Also, make sure to run cargo clippy and cargo clippy -- -Dwarnings to ensure there are no errors left. Thanks.

For more information about Conventional Commits, prefer this guide.

If you have questions or need help, feel free to contact us:
📧 Email: [email protected]
💬 Discord: Join Here

Steps to Contribute

1. 🍽️ Fork the Repository

• Go to the Carch GitHub page.
• Click the Fork button in the top-right corner to create your own copy of the repository.

2. 🌿 Clone the Forked Repository

• Use the following command to clone the repository to your local system:

  git clone https://github.com/your-username/carch.git

• Replace your-username with your GitHub username.

💡 TIP

You can also use GUI tools like GitHub Desktop or even the GitHub web interface to fork and clone repositories. These tools provide an easy-to-use visual interface for managing your contributions.

3. 🌱 Set the Original Repository as Upstream

• Add the original Carch repository as an upstream remote to keep your fork up to date:

  cd carch

  git remote add upstream https://github.com/original-author/carch.git

4. 🍇 Create a New Feature Branch

• Before making changes, create a new branch with a descriptive name:

  git checkout -b feature/your-branch-name

• Examples of branch names:

  • feature/add-new-script
  • bugfix/fix-installation-issue

5. 🔧 Make Your Changes

• Implement the necessary changes to the code or documentation.
• Ensure that your changes are clear, tested, and follow the project's coding standards.

6. 📝 Stage and Commit Your Changes

• Add the modified files to the staging area:

  git add .

• Commit your changes with a clear message:

  git commit -m "Add: [brief description of your changes]"

7. 🚀 Push the Changes to Your Fork

• Push your branch to your forked repository:

  git push origin feature/your-branch-name

8. 📥 Submit a Pull Request (PR)

• Go to the original Carch repository on GitHub.
• Click on New Pull Request.
• Select your branch from the dropdown and describe your changes in detail.
• Submit the PR for review!

📚 Contributing to Carch Docs

Carch Docs is ➥ Live Here

🚀 Ways to Contribute

You can contribute by:

• 🪛 Fixing typos or mistakes in existing guides
• 🌐 Translating the documentation into other languages (highly encouraged!)

🌍 Translating Documentation

Want to help make Carch accessible to users worldwide? Help us translate the docs!

If you're contributing a new language, follow these steps:

1. 📁 Create a new folder for your language inside the docs/ directory. Use ISO 639-1 codes (e.g. fr, es, hi, etc.).
2. 🛠️ Translate the Markdown content inside the new folder.
3. 🧩 Modify docs/.vitepress/config.ts:
   • Add your language in the locales section.
   • Provide a label, lang, and link for navigation.

🧪 Testing Your Changes Locally

To preview your changes:

bun install
bun run docs:dev

IMPORTANT

Please open an issue first if you plan to introduce major structural or organizational changes. We’d love to discuss and collaborate on it beforehand!

🧾 Commit Style

Use clear commit messages like:

git commit -m "fix(docs): correct typo in installation guide"
git commit -m "feat(docs): add Hindi translation"

More on Conventional Commits.

🙌 Thanks for helping improve the documentation!

Guidelines

Code Quality

• Follow the existing coding style of the project.
• Write clear, concise, and well-documented code.

Testing

• Test your changes locally to ensure they work as expected.
• If your changes introduce new features, add necessary tests where applicable.

Documentation

• If your changes involve new functionality, update the relevant documentation.
• Ensure the README or Wiki reflects your updates.

Syncing Your Fork

• Keep your fork updated to avoid conflicts:

  git fetch upstream

  git merge upstream/main

  • Replace main with the default branch of the repository if it's different.

Thank you for contributing to Carch! Your effort helps make this project better for everyone.