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 script
of Carch is located in:
build/carch
- All
additional
scripts of Carch are stored in:
scripts/*.sh
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.
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:
bashgit 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:
bashcd carch
bashgit 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:
bashgit 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:
bashgit add .
Commit your changes with a clear message:
bashgit commit -m "Add: [brief description of your changes]"
7. π Push the Changes to Your Fork β
Push your branch to your forked repository:
bashgit 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:
bashgit fetch upstream
bashgit merge upstream/main
- Replace
main
with the default branch of the repository if itβs different.
- Replace
Thank you for contributing to Carch! Your effort helps make this project better for everyone.