Skip to content

The folder we will include on all our repositries

License

Notifications You must be signed in to change notification settings

tumblenet/repository-template

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

73 Commits
 
 
 
 
 
 

Repository files navigation

Project Name

TODO:A description of your project follows. A good description is clear, short, and to the point. Describe the importance of your project, and what it does.

Table of Contents

TODO: Optionally, include a table of contents in order to allow other people to quickly naviagte especially long or detailed READMEs.

Getting Started

These instructions will get you a copy of the project up and running on your local machine. See deployment for notes on how to deploy the project on a live system.

Prerequisites

(Preperatrion to install)

Installation

Installation is the next section in an effective README. Tell other users how to install your project locally. Optionally, include a gif to make the process even more clear for other people.

Usage

TODO: The next section is usage, in which you instruct other people on how to use your project after they’ve installed it. This would also be a good place to include screenshots of your project in action.

Running the tests

How to test wheather the product works

Deployment

Add additional notes about how to deploy this on a live system

Built With

  • List of things used to build product

Contributing

Please read CONTRIBUTING.md for details on our code of conduct, and the process for submitting pull requests to us.

Larger projects often have sections on contributing to their project, in which contribution instructions are outlined. Sometimes, this is a separate file. If you have specific contribution preferences, explain them so that other developers know how to best contribute to your work. To learn more about how to help others contribute, check out the guide for (setting guidelines for repository contributors)[https://help.github.com/articles/setting-guidelines-for-repository-contributors/].

Versionin

Say what versioning method you use.

example: We use SemVer for versioning. For the versions available, see the tags on this repository.

Authors

  • AuthorName - What they do - USER

See also the list of contributors who participated in this project.

License

TODO: Finally, include a section for the license of your project. For more information on choosing a license, check out GitHub’s licensing guide!

Acknowledgments

About

The folder we will include on all our repositries

Topics

Resources

License

Stars

Watchers

Forks

Packages

No packages published