Skip to content

ExpressHermes/Primitive-Paint

Repository files navigation

Primitive Paint

GitHub stars GitHub forks GitHub watchers Repo. Size

GitHub contributors GitHub Closed issues GitHub PR Open GitHub PR closed GitHub language count GitHub top language GitHub last commit GitHub Maintained Open Source


A simple paint web app using paperjs.
Visit the Official Website »

Report Bug · Request Feature

Table of Contents :


About Primitive Paint

A simple paint web app using paperjs, site can be found here » . Checkout the snapshots of this project ( which are given below ) , As you see you can draw so much awesome and creative things with the help of "Primitive Paint" . And if you want to contribute in this project. Refers the " Contribution Guidelines " and get started .

Tech-Stack used :

HTML 5 CSS3


Primitive Paint - checkout us.



(back to top)

Open Source programs this repo has been part of



(back to top)

Contribution Guidelines

Never made an open source contribution before? Here's a quick rundown!
  • Find an issue that you are interested in addressing or a feature that you would like to add.

  • Fork the repository associated with the issue to your local GitHub organization. This means that you will have a copy of the repository under your-GitHub-username/repository-name.

  • Clone the repository to your local machine using git clone .

  • Create a new branch for your fix using git checkout -b branch-name-here.

  • Make the appropriate changes for the issue you are trying to address or the feature that you want to add.

  • Use git add insert-paths-of-changed-files-here to add the file contents of the changed files to the "snapshot" git uses to manage the state of the project, also known as the index.

  • Use git commit -m "Insert a short message of the changes made here" to store the contents of the index with a descriptive message.

  • Push the changes to the remote repository using git push origin branch-name-here.

  • Submit a pull request to the upstream repository.

  • Title the pull request with a short description of the changes made and the issue or bug number associated with your change. For example, you can title an issue like so "Added more log outputting to resolve #4352".

  • In the description of the pull request, explain the changes that you made, any issues you think exist with the pull request you made, and any questions you have for the maintainer. It's OK if your pull request is not perfect (no pull request is), the reviewer will be able to help you fix any problems and improve it!

  • Wait for the pull request to be reviewed by a maintainer.

  • Make changes to the pull request if the reviewing maintainer recommends them.

  • Celebrate 🥳 your success after your pull request is merged!

Refers to CONTRIBUTING.md. For more information about, How you can contribute in this awesome project.

(back to top)

Contributors

Thanks to all the people who contribute

Contributors



(back to top)

Show some ❤️ by starring this awesome repositorie!