Skip to content

Latest commit

 

History

History
52 lines (34 loc) · 1.93 KB

CONTRIBUTING.md

File metadata and controls

52 lines (34 loc) · 1.93 KB

Contribution Guidelines for CyberPath

We appreciate your interest in contributing to CyberPath! To ensure a smooth and effective collaboration, please follow these guidelines.

How to Contribute

  1. Fork the Repository: Start by forking the CyberPath repository to your own GitHub account.

  2. Create a Branch: Create a new branch for your feature or bug fix. Use descriptive names for your branches:

    git checkout -b feature/YourFeatureName

  3. Make Changes: Implement your changes in the new branch. Ensure that your code adheres to our coding standards.

  4. Write Tests: If applicable, write tests for your changes to ensure they work as intended.

  5. Commit Your Changes: Commit your changes with a clear and concise commit message:

    git commit -m "Add feature/bug fix description"

  6. Push Your Changes: Push your changes back to your forked repository:

    git push origin feature/YourFeatureName

  7. Open a Pull Request: Navigate to the original CyberPath repository and open a pull request. Provide a detailed description of your changes and why they should be merged.

Code of Conduct

Please adhere to our Code of Conduct in all interactions within the CyberPath community.

Review Process

  • All contributions will be reviewed by maintainers.
  • Feedback may be provided, and you may be asked to make adjustments before merging.

Issues and Feature Requests

If you encounter any issues or have suggestions for new features, please open an issue in the GitHub repository. Provide as much detail as possible to help us understand the problem or request.

Thank You!

Thank you for considering contributing to CyberPath! Your efforts help us build a better resource for everyone in the cybersecurity community.

For additional information refer to the contributors page