Contributing

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.

Caution

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

Before contributing, understand the structure of Carch:

1. The main script of Carch is located in:

   • Directorybuild/

     • carch

2. All additional scripts of Carch are stored in:

   • Directoryscripts/

     • Alacritty.sh
     • Aur.sh
     • Bash.sh
     • Bun.sh
     • Dwm.sh
     • Fastfetch.sh
     • Fish.sh
     • Fonts.sh
     • Grub.sh
     • Helix.sh
     • Hyprland.sh
     • i3wm.sh
     • Kitty.sh
     • LTS-Kernel.sh
     • Neovim.sh
     • Npm.sh
     • Packages.sh
     • Picom.sh
     • Rofi.sh
     • Sddm.sh
     • SwayWM.sh
     • Themes-Icons.sh
     • Tmux.sh
     • Wallpapers.sh
     • Zsh.sh

Tip

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.

If you have questions or need help, feel free to contact us:
📧 Email: harilvfs@chalisehari.com.np
💬 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!

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.