|
| 1 | +## Issues |
| 2 | + |
| 3 | +When reporting a possible bug, please provide detail steps so that we will be able |
| 4 | +to reproduce the issue. Please try not to use phrases like "very big bug", |
| 5 | +"huge issue", etc. No need to use exclamation marks as well. |
| 6 | + |
| 7 | +Note that we don't provide developer help or any kind of support on GitHub. |
| 8 | +For this, please use our [forum](https://forum.espocrm.com). |
| 9 | + |
1 | 10 | ## Pull Requests |
2 | 11 |
|
| 12 | +If you would like to contribute something that is not a small fix, please create an issue first |
| 13 | +(a bug report or feature request). |
| 14 | + |
3 | 15 | Before we can merge your pull request, you need to accept our CLA [here](https://github.com/espocrm/cla). |
4 | 16 |
|
5 | 17 | It's desirable that one PR solves one specific problem. Do not include code style changes to PRs |
6 | 18 | (unless the main purpose of the PR is a code style fix). |
7 | 19 |
|
8 | | -If you would like to contribute something that is not a small fix, it's reasonable to create an issue first |
9 | | -(a bug report or feature request). |
10 | | - |
11 | 20 | Branches: |
12 | 21 |
|
13 | 22 | * *master* – the develop branch; new features should be pushed to here; |
14 | 23 | * *fix* – the upcoming maintenance release; small fixes should be pushed to here. |
15 | | - |
16 | | -## Issues |
17 | | - |
18 | | -We'd appreciate if you prefer posting issues on weekdays rather than weekends. |
19 | | - |
20 | | -When reporting a possible bug, please provide detail steps so that we will be able |
21 | | -to reproduce the issue. Please try not to use phrases like "very big bug", |
22 | | -"huge issue", etc. No need to use exclamation marks as well. |
23 | | - |
24 | | -Note that we don't provide developer help or any kind of support on GitHub. |
25 | | -For this, please use our [forum](https://forum.espocrm.com). |
0 commit comments