Skip to content

Latest commit

 

History

History
executable file
·
51 lines (32 loc) · 2.67 KB

CONTRIBUTING.md

File metadata and controls

executable file
·
51 lines (32 loc) · 2.67 KB
Raw

Contribution Guidelines

Thanks for taking the time to contribute 👍

We accept contributions via Pull Requests on GitHub.

The following is a set of guidelines for contributing to Awesome TensorFlowJS. These are just guidelines, not rules, use your best judgment and feel free to propose changes to this project.

🛠 How to Contribute

🩹Create an issue

Do you know any cool TensorFlow.js project that aren't in this list? Isn't on the open issues or pull requests? Please create a new issue or submit a pull request, we will be happy to receive it!

💖 Submit a Pull Request

  • Sync - Please make sure your repository is up to date with ours to avoid conflicts as much as possible.
  • Language - Please make sure to check your contribution for grammar mistakes and typos as much as possible.
  • One pull request per feature - If you want to do more than one thing, send multiple pull requests.
  • Send coherent history - Make sure each individual commit in your pull request is meaningful. If you had to make multiple intermediate commits while developing, please squash them before submitting.

👍Voting and commenting 🗣

Just use GitHub reactions and comments to express your feelings/experience about open suggestions (additions or removals).

📚 Guidelines

  • Please search previous suggestions before making a new one, as yours may be a duplicate.
  • Use the following format: [Project Name](http://example.com/) - A short description.
  • The link should be the name of the package or project.
  • Links and categories should be sorted alphabetically.
  • Add one link per pull-request.
  • Keep descriptions sentence case, concise, clear and simple, and end them with a period/stop.
  • Check your spelling and grammar.
  • New categories, or improvements to the existing ones are also welcome.
  • Make sure your text editor is set to remove trailing whitespace.

Thank you for contributing

We welcome all contributions from everyone, but make sure you read our Code of Conduct.

Upon contributing, you agree to abide by the following:

  • You agree to abide by the Code of Conduct at all times.
  • You spellchecked your text with either Grammarly (AI-powered writing tool) or yourself.
  • If necessary, you have added a short, but descriptive description after the link, with proper punctuation.

Thank you for contributing! I look forward to reviewing your PR! 🔮