-
Notifications
You must be signed in to change notification settings - Fork 14
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #42 from joselitofilho/new/v0.0.17
New/v0.0.17
- Loading branch information
Showing
7 changed files
with
2,022 additions
and
19 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,74 @@ | ||
# Contributor Covenant Code of Conduct | ||
|
||
## Our Pledge | ||
|
||
In the interest of fostering an open and welcoming environment, we as | ||
contributors and maintainers pledge to making participation in our project and | ||
our community a harassment-free experience for everyone, regardless of age, body | ||
size, disability, ethnicity, gender identity and expression, level of experience, | ||
nationality, personal appearance, race, religion, or sexual identity and | ||
orientation. | ||
|
||
## Our Standards | ||
|
||
Examples of behavior that contributes to creating a positive environment | ||
include: | ||
|
||
- Using welcoming and inclusive language | ||
- Being respectful of differing viewpoints and experiences | ||
- Gracefully accepting constructive criticism | ||
- Focusing on what is best for the community | ||
- Showing empathy towards other community members | ||
|
||
Examples of unacceptable behavior by participants include: | ||
|
||
- The use of sexualized language or imagery and unwelcome sexual attention or | ||
advances | ||
- Trolling, insulting/derogatory comments, and personal or political attacks | ||
- Public or private harassment | ||
- Publishing others' private information, such as a physical or electronic | ||
address, without explicit permission | ||
- Other conduct which could reasonably be considered inappropriate in a | ||
professional setting | ||
|
||
## Our Responsibilities | ||
|
||
Project maintainers are responsible for clarifying the standards of acceptable | ||
behavior and are expected to take appropriate and fair corrective action in | ||
response to any instances of unacceptable behavior. | ||
|
||
Project maintainers have the right and responsibility to remove, edit, or | ||
reject comments, commits, code, wiki edits, issues, and other contributions | ||
that are not aligned to this Code of Conduct, or to ban temporarily or | ||
permanently any contributor for other behaviors that they deem inappropriate, | ||
threatening, offensive, or harmful. | ||
|
||
## Scope | ||
|
||
This Code of Conduct applies both within project spaces and in public spaces | ||
when an individual is representing the project or its community. Examples of | ||
representing a project or community include using an official project e-mail | ||
address, posting via an official social media account, or acting as an appointed | ||
representative at an online or offline event. Representation of a project may be | ||
further defined and clarified by project maintainers. | ||
|
||
## Enforcement | ||
|
||
Instances of abusive, harassing, or otherwise unacceptable behavior may be | ||
reported by contacting the project team at [[email protected]](mailto:[email protected]). All | ||
complaints will be reviewed and investigated and will result in a response that | ||
is deemed necessary and appropriate to the circumstances. The project team is | ||
obligated to maintain confidentiality with regard to the reporter of an incident. | ||
Further details of specific enforcement policies may be posted separately. | ||
|
||
Project maintainers who do not follow or enforce the Code of Conduct in good | ||
faith may face temporary or permanent repercussions as determined by other | ||
members of the project's leadership. | ||
|
||
## Attribution | ||
|
||
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, | ||
available at [http://contributor-covenant.org/version/1/4][version] | ||
|
||
[homepage]: http://contributor-covenant.org | ||
[version]: http://contributor-covenant.org/version/1/4/ |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,104 @@ | ||
# Contributing | ||
|
||
By participating to this project, you agree to abide our [code of | ||
conduct](CODE_OF_CONDUCT.md). | ||
|
||
**Table of Contents** | ||
|
||
- [Setup your machine](#setup-your-machine) | ||
- [Using docker](#using-docker) | ||
- [Generate database](#generate-database) | ||
- [Run server](#run-server) | ||
- [Visual Studio Code](#visual-studio-code) | ||
- [Create a commit](#create-a-commit) | ||
- [Submit a pull request](#submit-a-pull-request) | ||
- [Credits](#credits) | ||
|
||
## Setup your machine | ||
|
||
### Using docker | ||
|
||
First time only: | ||
```bash | ||
docker-compose build | ||
``` | ||
|
||
Run container: | ||
```bash | ||
docker-compose up -d | ||
``` | ||
|
||
Enter on container: | ||
```bash | ||
docker-compose exec server bash | ||
``` | ||
|
||
## Visual Studio Code | ||
|
||
If you are using VS Code, I strongly recommend you install the following plugin: | ||
- [Remote - Containers](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers) - use a Docker container as a full-featured development environment. | ||
- [ESLint plugin for VS Code](https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint) - which will enable you to view ESLint errors directly in your editor. | ||
|
||
To unleash the true powers of ESLint and Prettier, we can configure VS Code so that it auto-corrects ESLint errors. | ||
You should tell VS Code not to formatOnSave, but instead fix ESLint errors on save. | ||
```json | ||
// .vscode/settings.json | ||
{ | ||
"editor.formatOnSave": false, | ||
"editor.codeActionsOnSave": { | ||
"source.fixAll.eslint": true | ||
} | ||
} | ||
``` | ||
|
||
## Build | ||
|
||
Install dependencies: | ||
```bash | ||
yarn | ||
``` | ||
|
||
## Deploy | ||
|
||
Install dependencies: | ||
```bash | ||
yarn install | ||
``` | ||
|
||
Packages extension: | ||
```bash | ||
vsce package | ||
``` | ||
|
||
Publishes extension: | ||
```bash | ||
vsce pulish | ||
``` | ||
|
||
## Create a commit | ||
|
||
Commit messages should be well formatted, and to make that "standardized", we | ||
are using Conventional Commits. | ||
|
||
You can follow the documentation on | ||
[their website](https://www.conventionalcommits.org). | ||
|
||
## Submit a pull request | ||
|
||
- go to a new branch | ||
```bash | ||
git checkout -b feat/my-feature | ||
``` | ||
- make your changes | ||
- run tests and linter again | ||
```bash | ||
yarn lint | ||
``` | ||
- Push your branch to [`surf-king`](https://github.com/board-games-jf/surf-king) repository | ||
- Open PR against the main branch. 🏄 | ||
|
||
## Credits | ||
|
||
### Contributors | ||
|
||
Thank you to all the people who have already contributed to `surf-king`! |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.