updated README and LICENSE
All checks were successful
CSGOWTF/csgowtf/pipeline/head This commit looks good

This commit is contained in:
2022-01-31 01:25:06 +01:00
parent a9a7dbcfff
commit fc10d9de09
2 changed files with 247 additions and 21 deletions

View File

@@ -1,24 +1,18 @@
# csgowtf
# CSGOW.TF
[![](https://img.shields.io/badge/license-GPL3-blue)](https://git.harting.dev/CSGOWTF/csgowtf/src/branch/master/LICENSE) [![](https://img.shields.io/liberapay/patrons/CSGOWTF.svg?logo=liberapay)](https://liberapay.com/CSGOWTF/)
## Project setup
```
yarn install
```
Statistics for CS:GO matchmaking matches.
### Compiles and hot-reloads for development
```
yarn serve
```
## Backend
This is the frontend to the [csgowtfd](https://git.harting.dev/CSGOWTF/csgowtfd) backend.
### Compiles and minifies for production
```
yarn build
```
### Lints and fixes files
```
yarn lint
```
### Customize configuration
See [Configuration Reference](https://cli.vuejs.org/config/).
## Tips on how to contribute
- If you are implementing or fixing an issue, please comment on the issue so work is not duplicated.
- If you want to implement a new feature, create an issue first describing the issue, so we know about it.
- Don't commit unnecessary changes to the codebase or debugging code.
- Write meaningful commits or squash them.
- Please try to follow the code style of the rest of the codebase.
- Only make pull requests to the dev branch.
- Only implement one feature per pull request to keep it easy to understand.
- Expect comments or questions on your pull request from the project maintainers. We try to keep the code as consistent and maintainable as possible.
- Each pull request should come from a new branch in your fork, it should have a meaningful name.