Project name is a <utility/tool/feature> that allows <insert_target_audience> to do <action/task_it_does>.
Your introduction should be around 2 or 3 sentences. Don't go overboard, people won't read it.
| Codebase | Description |
|---|---|
| Frontend Tournament | Nuxt.js Frontend |
| Backend Tournament | Nest.js API |
- development -> pr this branch for everything else
- staging -> It'll connect to as many services as it can without touching the prod environment.
- main -> don't touch, this is what's running in prod
The code of conduct is described in CODE_OF_CONDUCT.md.
Before you begin, ensure you have met the following requirements:
- You have installed the latest version of
<coding_language/dependency/requirement_1> - You have a
<Windows/Linux/Mac>machine. State which OS is supported/which is not. - You have read
<guide/link/documentation_related_to_project>.
To install <project_name>, follow these steps:
Linux and macOS:
<install_command>
Windows:
<install_command>
To use <project_name>, follow these steps:
# enter the project directory
cd project_name
# pull from latest staging
git pull main
# install dependency
npm install
# develop
npm run devAdd run commands and examples you think users will find useful. Provide an options reference for bonus points!
# unit tests
$ npm run test
# e2e tests
$ npm run test:e2e
# test coverage
$ npm run test:cov# preview the release environment effect
npm run preview
# preview the release environment effect + static resource analysis
npm run preview -- --report
# code format check
npm run lint
# code format check and auto fix
npm run lint -- --fixfor running in your machine, please prepare your .env
Development
BASE_URL_API_TOURNAMENT=
BASE_URL_SPORTIV=
SRC_URL_SPORTIV=Production
BASE_URL_API_TOURNAMENT=
BASE_URL_SPORTIV=
SRC_URL_SPORTIV=Hello engineers! We want to make contributing to this project as easy and transparent as possible, whether it's:
- Reporting an issue
- Discussing the current state of the code
- Submitting a fix
- Proposing new updates
To contribute to <project_name>, follow these steps:
- Clone this repository.
- Create a branch:
git checkout -b <branch_name>. - Add Changes:
git add -A. - Make your changes and commit them:
git commit -m -S '<commit_message>' - Push to the original branch:
git push - Create the pull request.
Alternatively see the GitHub documentation on creating a pull request.
Thanks to the following people who have contributed to this project:
- @andikaleonardo π½
You might want to consider using something like the All Contributors specification and its emoji key.
If you want to contact me you can reach me at your_email@address.com.
This project uses the following license: <license_name>.
