| 1 | # Contributing to Fomantic-UI
|
| 2 |
|
| 3 | ### :notebook: Support Questions
|
| 4 |
|
| 5 | Questions regarding usage and support can be asked in [GitHub Issues](https://github.com/fomantic/Fomantic-UI/issues) but if your question starts to become a conversation we will ask you to move it into our [Discord](https://discordapp.com/invite/YChxjJ3). If you are looking for quick support [Discord](https://discordapp.com/invite/YChxjJ3) is the best place to ask.
|
| 6 |
|
| 7 | After asking your question you may find that it is actually a bug or a feature which doesn't exist. At this point it's a good idea to submit a GitHub issue (if you haven't already) to request/report your issue. When you open an issue please use the issue templates and fill in as many of the sections as you can. This helps us triage issues without needing to ask lots of questions.
|
| 8 |
|
| 9 | ### Bugs & Enhancements
|
| 10 |
|
| 11 | #### :bug: Reporting Bugs
|
| 12 |
|
| 13 | We use [GitHub Issues](https://github.com/fomantic/Fomantic-UI/issues) to track all bugs and enhancements for FUI, before raising a bug please check to see if it has already been raised. If you find it has already been raised add a :thumbsup: to the issue reactions to show you are also having the same issue. Please do not spam "+1", "bump" etc.
|
| 14 |
|
| 15 | If you find that your issue has not already been raised please create a [new issue](https://github.com/fomantic/Fomantic-UI/issues/new?template=Bug_report.md) and please follow the template provided.
|
| 16 |
|
| 17 | When creating an issue you will be asked to create a [JSFiddle](https://jsfiddle.net/31d6y7mn) to replicate your issue. You can fork [this template](https://jsfiddle.net/31d6y7mn) which has the latest version of Fomantic ready to use.
|
| 18 |
|
| 19 | #### :crystal_ball: Requesting Features
|
| 20 |
|
| 21 | We also use [GitHub Issues](https://github.com/fomantic/Fomantic-UI/issues) for new feature requests. Before submitting a new issue please check to see if it has already been requested. If you find that your issue has not already been requested feel free create a [new issue](https://github.com/fomantic/Fomantic-UI/issues/new?template=Feature_request.md) and please follow the template provided. This helps us triage issues without needing to ask lots of questions.
|
| 22 |
|
| 23 | When you create the issue please when possible include pictures or a [JSFiddle](https://jsfiddle.net/31d6y7mn), this can help contributors understand what your asking.
|
| 24 |
|
| 25 | ##### Naming Issues
|
| 26 |
|
| 27 | When you create an issue please follow our naming convention this makes it easy to scan over issues.
|
| 28 |
|
| 29 | **Bugs:** [Scope] x does not do y
|
| 30 | **Enhancements:** [Scope] x should do y
|
| 31 |
|
| 32 | The scope is the component which has the issue or enhancement e.g. Segment, Grid, Dropdown etc. when you describe the issue in the summary keep it brief 60 characters max.
|
| 33 |
|
| 34 | ##### Tracking Issue Progress
|
| 35 |
|
| 36 | As bugs and features are triaged they will be assigned to milestones. The best indication of when a change will land is to check the date on the [upcoming milestones](https://github.com/fomantic/Fomantic-UI/milestones) page.
|
| 37 |
|
| 38 | ### :pencil: Pull Requests Guide
|
| 39 |
|
| 40 | **All pull requests should be merged into the `develop` branch. Make sure your branch is based from our develop branch and not the master.**
|
| 41 |
|
| 42 | Anyone can jump on the issues board and grab off bugs to fix. This is probably the best way to become a contributor to Fomantic. We only ask you to stick to these few rules to make it easier to merge/process your pull requests.
|
| 43 |
|
| 44 | - When you implement a new feature or fix a bug think about backwards compatibility. If your change is backwards compatible it is most likely to be merged sooner since you won't need to wait for a breaking change update.
|
| 45 | - Please commit using the [AngularJS Git Commit Message Convention](https://gist.github.com/stephenparish/9941e89d80e2bc58a153) this is more of a nice to have and isn't required.
|
| 46 | - Please try and stick to a similar code style so everyone can read your code.
|
| 47 | - When you commit don't include your dist files, this can cause merge conflicts and also adds unnecessary changes to the PR.
|
| 48 |
|
| 49 | #### Setup your enviroment
|
| 50 | These few steps are the easiest way to setup your dev environment.
|
| 51 |
|
| 52 | 1. Fork the [main repository](https://github.com/fomantic/Fomantic-UI).
|
| 53 | 2. Clone your fork and add the main repository as a remote
|
| 54 | ```bash
|
| 55 | $ git clone https://github.com/<YOUR_GITHUB_USERNAME>/Fomantic-UI.git
|
| 56 | $ cd Fomantic-UI
|
| 57 | $ git remote add fui https://github.com/fomantic/Fomantic-UI.git
|
| 58 | $ git fetch fui
|
| 59 | ```
|
| 60 | 3. Checkout a new branch with the FUI `develop` branch as the base
|
| 61 | ```bash
|
| 62 | $ git checkout -b <BRANCH_NAME> fui/develop
|
| 63 | ```
|
| 64 |
|
| 65 | Now you can start working on your change. Once you submit your PR remember to merge into the `develop` branch NOT `master`.
|
| 66 |
|
| 67 | ### The [CONTRIBUTORS](CONTRIBUTORS.md) list
|
| 68 |
|
| 69 | Once you contribute to the project you can be added the the contributors list for any categories you have contributed towards. If you think you should be on the list but aren't already you can request to be added via the [`all-contributors` bot](https://allcontributors.org/docs/en/bot/overview).
|