Commit df10524c authored by ltngames's avatar ltngames 馃専

馃摑 Chore 馃敟 add issue/MR templates, license and contributing guide

parent bdfca4e7
......@@ -47,6 +47,6 @@ build:
- bin
- tags
- master
- npm run build
\ No newline at end of file
<!--- Provide a general summary of the issue in the Title above -->
## Description
<!--- Provide a more detailed introduction to the issue itself, and why you consider it to be a bug -->
## Expected Behavior
<!--- Tell us what should happen -->
## Actual Behavior
<!--- Tell us what happens instead -->
## Possible Fix
<!--- Not obligatory, but suggest a fix or reason for the bug -->
## Steps to Reproduce
<!--- Provide a link to a live example, or an unambiguous set of steps to -->
<!--- reproduce this bug. Include code to reproduce, if relevant -->
## Context
<!--- How has this bug affected you? What were you trying to accomplish? -->
## Your Environment
<!--- Include as many relevant details about the environment you experienced the bug in -->
* Version used:
* Operating System and version:
* Link to your project:
<!--- Provide a general summary of the issue in the Title above -->
## Description
<!--- Provide a detailed description of the change or addition you are proposing -->
## Why is this change important
<!--- Why is this change important to you? How would you use it? -->
<!--- How can it benefit other users? -->
## Possible Implementation
<!--- Not obligatory, but suggest an idea for implementing addition or change -->
<!--- Provide a general summary of your changes in the Title above -->
## Description
<!--- Describe your changes in detail -->
## Related Issue
<!--- This project only accepts pull requests related to open issues -->
<!--- If suggesting a new feature or change, please discuss it in an issue first -->
<!--- If fixing a bug, there should be an issue describing it with steps to reproduce -->
<!--- Please link to the issue here: -->
## Motivation and Context
<!--- Why is this change required? What problem does it solve? -->
## How Has This Been Tested?
<!--- Please describe in detail how you tested your changes. -->
<!--- Include details of your testing environment, and the tests you ran to -->
<!--- see how your change affects other areas of the code, etc. -->
## Screenshots (if appropriate):
<!--- Remove the heading if no screenshot is available -->
## Types of changes
<!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
<!--- Feel free to add or remove from the list -->
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to change)
## Checklist:
<!--- Go over all the following points, and put an `x` in all the boxes that apply. -->
<!--- Feel free to add or remove from the list -->
- [ ] My change requires a change to the documentation.
- [ ] I have updated the documentation accordingly.
- [ ] I have added tests to cover my changes.
# Contributing to fenix-engine-cli
鉁 Thanks for contributing to **FeniXEngine - FeniXCLI**! 鉁
As a contributor, here are the guidelines we would like you to follow:
- [How can I contribute?](#how-can-i-contribute)
- [Using the issue tracker](#using-the-issue-tracker)
- [Submitting a Merge Request](#submitting-a-merge-request)
- [Coding rules](#coding-rules)
- [Commit message guidelines](#commit-message-guidelines)
- [Working with the code](#working-with-the-code)
We also recommend that you read [How to Contribute to Open Source](
## How can I contribute?
### Improve documentation
As a **fenix-engine-cli** user, you are the perfect candidate to help us improve our documentation: typo corrections, clarifications, more examples, etc. Take a look at the [documentation issues that need help]([]=documentation).
Please follow the [Documentation guidelines](#documentation).
### Give feedback on issues
Some issues are created without information requested in the [Bug report guideline](#bug-report). Help make them easier to resolve by adding any relevant information.
Issues with the [design label]n) are meant to discuss the implementation of new features. Participating in the discussion is a good opportunity to get involved and influence the future direction of **fenix-engine-cli**.
### Fix bugs and implement features
Confirmed bugs and ready-to-implement features are marked with the [help wanted label]([]=help%20wanted). Post a comment on an issue to indicate you would like to work on it and to request help from the [@fenix-engine-cli/maintainers]() and the community.
## Using the issue tracker
The issue tracker is the channel for [bug reports](#bug-report), [features requests](#feature-request) and [submitting merge requests](#submitting-a-merge-request) only.
Before opening an issue or a Merge Request, please use the [Gitlab issue search]( to make sure the bug or feature request hasn't been already reported or fixed.
### Bug report
A good bug report shouldn't leave others needing to chase you for more information. Please try to be as detailed as possible in your report and fill the information requested in the [Bug report template](
### Feature request
Feature requests are welcome, but take a moment to find out whether your idea fits with the scope and aims of the project. It's up to you to make a strong case to convince the project's developers of the merits of this feature. Please provide as much detail and context as possible and fill the information requested in the [Feature request template](
## Submitting a Merge Request
Good merge requests, whether patches, improvements, or new features, are a fantastic help. They should remain focused in scope and avoid containing unrelated commits.
**Please ask first** before embarking on any significant merge requests (e.g. implementing features, refactoring code), otherwise you risk spending a lot of time working on something that the project's developers might not want to merge into the project.
If you have never created a merge request before, welcome 馃帀 馃槃. [Here is a great tutorial]( on how to send one :)
Here is a summary of the steps to follow:
1. [Set up the workspace](#set-up-the-workspace)
2. If you cloned a while ago, get the latest changes from upstream and update dependencies:
$ git checkout master
$ git pull upstream master
$ rm -rf node_modules
$ npm install
3. Create a new topic branch (off the main project development branch) to contain your feature, change, or fix:
$ git checkout -b <topic-branch-name>
4. Make your code changes, following the [Coding rules](#coding-rules)
5. Push your topic branch up to your fork:
$ git push origin <topic-branch-name>
6. [Open a Merge Request]( with a clear title and description.
- For ambitious tasks, open a Merge Request as soon as possible with the `[WIP]` prefix in the title, in order to get feedback and help from the community.
- [Allow fenix-engine-cli maintainers to make changes to your Merge Request branch]( This way, we can rebase it and make some minor changes if necessary. All changes we make will be done in new commit and we'll ask for your approval before merging them.
## Coding rules
### Source code
To ensure consistency and quality throughout the source code, all code modifications must have:
- No [linting](#lint) errors
- A [test](#tests) for every possible case introduced by your code change
- **100%** test coverage
- [Valid commit message(s)](#commit-message-guidelines)
- Documentation for new features
- Updated documentation for modified features
### Documentation
To ensure consistency and quality, all documentation modifications must:
- Refer to brand in [bold]( with proper capitalization, i.e. **GitHub**, **fenix-engine-cli**, **npm**
- Prefer [tables]( over [lists]( when listing key values, i.e. List of options with their description
- Use [links]( when you are referring to:
- a **fenix-engine-cli** concept described somewhere else in the documentation, i.e. How to [contribute](
- a third-party product/brand/service, i.e. Integrate with [GitHub](
- an external concept or feature, i.e. Create a [GitHub release](
- a package or module, i.e. The [`@fenix-engine-cli/github`]( module
- Use the the [single backtick `code` quoting]( for:
- commands inside sentences, i.e. the `fenix-engine-cli` command
- programming language keywords, i.e. `function`, `async`, `String`
- packages or modules, i.e. The [`@fenix-engine-cli/github`]( module
- Use the the [triple backtick `code` formatting]( for:
- code examples
- configuration examples
- sequence of command lines
### Commit message guidelines
#### Atomic commits
If possible, make [atomic commits](, which means:
- a commit should contain exactly one self-contained functional change
- a functional change should be contained in exactly one commit
- a commit should not create an inconsistent state (such as test errors, linting errors, partial fix, feature with documentation etc...)
A complex feature can be broken down into multiple commits as long as each one maintains a consistent state and consists of a self-contained change.
#### Git commit message conventions
FeniXEngine git commit message convention is a gentle mix between clear easy to ready messages with a bit of extra spunk and fun by using gitmoji commit standard.
Each commit message consists of a **title**, and a **message**. The header has a special format that includes a **emoji**, **type**, and a **subject**:
[emoji]<type> <subject>
Header format:
[:emoji:] <type> <subject>
The **emoji** is optional but you can consider starting the commit message with an applicable emoji in the list.
For a full list have a look at [Gitmoji]( 馃帹
| Emoji | Raw | Is for |
| 馃悰 | :bug: | Fixing a bug
| 鈿 | :zap: | Improving performance
| 鉁 | :sparkles | Adding a new feature
| 馃帹 | :art: | Improving structure/format of the code
| 馃敟 | :fire: | Removing code or files
| 馃摑 | :memo: | Writing documentation
| 鉁 | :white_checkmark | Adding tests
| 馃毀 | :construction: | Work in progress
| 馃敡 | :wrench: | Updating/Adding configuration files
| 馃挌 | :green_heart: | Fixing CI builds
To make commits with emoji's easier try out the [Gitmoji CLI](
#### Revert
If the commit reverts a previous commit, it should begin with `Revert: `, followed by the header of the reverted commit. The message should say: `This reverts commit <hash>.`, where the hash is the SHA of the commit being reverted.
#### Type
The **type** is mandatory in all commit messages and must begin with an uppercase letter:
| Type | Description |
| **Chore** | Changes that affect the build system or external dependencies (example scopes: eslint, npm) |
| **CI** | Changes to our CI configuration files and scripts |
| **Docs** | Documentation only changes |
| **Feat** | A new feature |
| **Fix** | A bug fix |
| **Perf** | A code change that improves performance |
| **Refactor** | A code change that neither fixes a bug nor adds a feature |
| **Style** | Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc) |
| **Test** | Adding missing tests or correcting existing tests |
#### Subject
The subject contains succinct description of the change:
* don't capitalize first letter
* no dot (.) at the end
* use the present tense ("Add feature" not "Added feature")
* use the imperative mood ("Move cursor to..." not "Moves cursor to...")
* limit the first line to 72 characters or less
#### Message
Just as in the **subject**, use the imperative, present tense: "change" not "changed" nor "changes".
The body should include the motivation for the change and contrast this with previous behavior.
It may also contain any information about **Breaking Changes** and is also the place to reference GitHub issues that this commit **Closes**.
**Breaking Changes** should start with the word `Breaking Change:` with a space or two newlines. The rest of the commit message is then used for this.
#### Examples
Remember this is a convention but don't take things so seriously, this is why we added the gitmoji standard to our commitm essage convention
馃悰Fix stop graphite breaking when too much pressure applied`
鉁‵eat add 'graphiteWidth' option`
Fix #42
鈿 Perf remove 馃敟 graphiteWidth option
BREAKING CHANGE 馃挜 The graphiteWidth option has been removed.
The default graphite width of 10mm is always used for performance reasons.
## Working with the code
### Lint
All the [fenix-engine-cli]( repositories use [Standard]
Before pushing your code changes make sure there are no linting errors with `npm run lint`. These changes will have to pass the repository pipeline before merge is accepted.
- Most linting errors can be automatically fixed with `npm run lint --fix`.
### Tests
All the [fenix-engine-cli]( repositories use [AVA]( for writing and running tests.
Before pushing your code changes make sure all **tests pass** and the **coverage is 100%**:
$ npm run test
**Tips:** During development you can:
- run only a subset of test files with `ava <glob>`, for example `ava test/mytestfile.test.js`
- run in watch mode with `ava -w` to automatically run a test file when you modify it
- run only the test you are working on by adding [`.only` to the test definition](
MIT License
Copyright (c) 2018 Contributors
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
\ No newline at end of file
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment