Skip to content

Latest commit

 

History

History
58 lines (29 loc) · 2.49 KB

CONTRIBUTING.md

File metadata and controls

58 lines (29 loc) · 2.49 KB

Contributing to xgeeks - SPLIT

🎉🚀🙌🏻 First off, thanks for taking the time to contribute! 🙌🏻🚀🎉

Thank you for considering contributing to this repository. It's people like you that make Open Source so great.

Please read our guidelines before you start.

Following these guidelines helps to communicate that you respect the time of the developers managing and developing this open source project. In return, they should reciprocate that respect in addressing your issue, assessing changes, and helping you finalize your pull requests.

Contributions we are looking for.

We keep an open mind! Improving documentation, bug triaging, or writing tutorials are all examples of helpful contributions that mean less work for you.

Ground Rules

Follow our Code of Conduct.

We expect everyone to abide by our Code of Conduct. Please read it. 🤝

Your First Contribution

Here are a couple of friendly tutorials to help you get started: http://makeapullrequest.com/ and http://www.firsttimersonly.com/

Working on your first Pull Request? You can learn how from this free series, How to Contribute to an Open Source Project on GitHub.

At this point, you're ready to make your changes! Feel free to ask for help; everyone is a beginner at first 😸

How to report a bug

If you find a security vulnerability, do NOT open an issue. Email contact@xgeeks.io instead.

Open an issue using the BUG template provided.

How to suggest a feature or enhancement

Open an issue using the FEATURE template provided.

Code review process

For your contribution to get accepted after it’s been submitted.

Your contribution will have to be Approved by a member of the Core Team before being merged.

The core team looks at Pull Requests on a regular basis. After feedback has been given we expect responses within two weeks. After two weeks we may close the pull request if it isn't showing any activity.

Code, commit message and labeling conventions

Commit message conventions.

We follow the conventional commits guidelines. Check here

PULL Requests

Opening pull requests should be done using the github template, with enough information and screenshots for visual changes to facilitate the reviewers job. Its MANDATORY to add a link to the issue related