Skip to content

CONTRIBUTING.md

Latest commit

 

History

History
52 lines (31 loc) · 2.29 KB

CONTRIBUTING.md

File metadata and controls

52 lines (31 loc) · 2.29 KB

Contributing to GoScheduler

First off, thank you for considering contributing to GoScheduler. We are committed to making GoScheduler a more scalable, reliable, and feature-enriched platform and your contributions will be highly valued.

Code of Conduct

By participating, you are expected to uphold our Code of Conduct. Please make sure to read and understand it before engaging with the community.

Types of Contributions

We are looking for a variety of different types of contributions including:

  • Bug reports
  • Feature requests
  • Code improvements
  • Documentation updates
  • And more!

Getting Started

To get started, we recommend that you familiarize yourself with the project and play around with it to check if it fits your needs. If you spot an issue or an area for improvement, we encourage you to open an issue or submit a pull request.

Discussing Changes

Please make sure to discuss the changes you wish to make via issue, email, or any other method with the owners of this repository before making a change. This helps us keep track of what everyone is doing and prevents unnecessary or duplicate work.

How to Submit Contributions

Here is a quick guide on how to contribute:

  1. Fork the repository and create your branch from main.
  2. If you've added code that should be tested, add tests.
  3. If you've changed APIs, update the documentation.
  4. Ensure the test suite passes.
  5. Make sure your code lints.
  6. Issue a pull request!

Review Process

Our team reviews pull requests on a biweekly basis. Please be patient while waiting for a review. We appreciate your contributions and will do our best to provide feedback and merge contributions in a timely manner.

Reporting Bugs & Requesting Features

When you are creating a bug report or feature request, please include as many details as possible. Include details of your environment or the context in which you encountered the bug and steps to reproduce it. For feature requests, explain what you're trying to achieve, and how your proposed change would help you.

Contact

For any queries, you can reach out to us at [goscheduler-support@myntra.com]. We look forward to your valuable suggestions and contributions!

Thank you for your interest in contributing to GoScheduler. We look forward to your contribution!