Skip to content

Latest commit

 

History

History
46 lines (30 loc) · 1.4 KB

CONTRIBUTING.md

File metadata and controls

46 lines (30 loc) · 1.4 KB

CONTRIBUTION GUIDELINES:

Contributing to Schedulo We love your input! We want to make contributing to Schedulo as easy and transparent as possible, whether it's:

  • Reporting a bug
  • Discussing the current state of the code
  • Submitting a fix
  • Proposing new features
  • Becoming a maintainer

Development Process

We use GitHub to host code, to track issues and feature requests, as well as accept pull requests.

  1. Fork the repo and create your branch from main.

  2. Clone the project to your local machine

  3. Create a new branch: checkout -b feature/your-feature-name

  4. Make your changes

  5. Push your changes to your fork

  6. Create a Pull Request

Pull Request Process

  • Update the README.md with details of changes if needed
  • Update documentation if you're changing functionality
  • Ensure your code follows the existing style
  • Make sure your code lints
  • Issue the pull request!

Templates

  • or issues, use our templates located at:

    • Bug reports: .github/ISSUE_TEMPLATE/bug_report.md
    • Feature requests: .github/ISSUE_TEMPLATE/feature_request.md

  • For pull requests, use the template at:.github/pull_request_template.md

Any contributions you make will be under the MIT Software License

When you submit code changes, your submissions are understood to be under the same MIT License that covers the project. If you have any concerns, please contact the maintainers.