All contributions to BJH OS are made via Pull Requests. Follow these steps:
- Clone the BJH OS repository locally:
git clone https://github.com/Haris16-code/BJH-OS.git - Create a new branch for your changes:
git checkout -b feature/my-new-feature - Make your changes locally and test thoroughly.
- Push your branch to the repository:
git push origin feature/my-new-feature - Go to the BJH OS repository on GitHub and click Compare & Pull Request.
- Fill out the Pull Request Template carefully, including:
- Summary of your changes
- Changes made
- How to test
- Related issues
- Screenshots (if UI-related)
- Submit the pull request targeting the main branch of BJH OS.
- Wait for review and respond to any feedback from maintainers.
Important: Do not push directly to main. All changes must go through a pull request.
- Follow the existing code style for JS, HTML, and CSS.
- Keep code clean and well-commented.
- Use meaningful variable and function names.
- For UI changes, ensure the design is consistent with BJH OS.
- Follow BJH OS coding and UI guidelines.
- Test your app or game thoroughly.
- Submit your project via the BJH OS Apps Deployment platform or repository.
- Include instructions on how to use or test the app/game.
- Read the detailed guide here: BJH OS Apps Market Guide
Check out the official guide from GitHub: How to Contribute to a Project on GitHub
For detailed developer guidelines, API documentation, and apps deployment instructions, see: BJH OS Developer Documentation
- Before submitting a new issue, check if it already exists.
- Use the Issue Templates (Bug Report / Feature Request) provided.
- Provide detailed information, screenshots, and steps to reproduce bugs.
- Submit new issues here: BJH OS Issues
By contributing, you agree to follow BJH OS’s Code of Conduct:
- Be respectful and professional
- Be constructive in feedback
- No spam or offensive content
We appreciate your contributions! BJH OS grows stronger with each contribution from the community. 🙌