Skip to content

Latest commit

 

History

History
55 lines (41 loc) · 2.23 KB

CONTRIBUTING.md

File metadata and controls

55 lines (41 loc) · 2.23 KB

Contributing Guide

Welcome to The Documentation Compendium! This guide will assist you in making valuable contributions to this project. Your efforts to improve and enhance our work are highly appreciated.

Overview

  • Understanding the Codebase: Familiarize yourself with the structure and organization of the project files. For a detailed overview, refer to our Codebase Structure.
  • Adhering to Standards: It's crucial that your contributions align with our established practices. Please review the Coding Guidelines to ensure compliance.

Making Contributions

Getting Started

  1. Fork the Repository:

  2. Create a New Branch:

    • Checkout a new branch for your work. Name it appropriately based on the nature of your contribution.
    • For example:
      $ git checkout -b BRANCH_NAME
      In case of any issues, you might need to update your local repository:
      $ git remote update && git fetch
    • It's best to use separate branches for different fixes or features.

Making Changes

  1. Commit Your Changes:

    • When making changes, ensure your git commit messages are clear and descriptive.
    • Follow our commit message conventions.
    • Commit these changes to your forked repository.
    • For example:
      $ git commit -am 'Add some feature or fix'
  2. Push Your Changes:

    • Push the changes to your branch.
    • For example:
      $ git push origin BRANCH_NAME

Submitting Your Changes

  1. Create a Pull Request:
    • Once you've pushed your changes, create a pull request (PR) to the fooBar branch of the main repository.
    • Ensure that your PR details the changes you've made and why they are necessary.
    • Our continuous integration system, Travis CI, will automatically check your submission.

By following these steps, your contribution should smoothly integrate with the main project. We look forward to your valuable input!