diff options
| author | 2019-12-15 14:08:49 +0100 | |
|---|---|---|
| committer | 2019-12-15 14:08:49 +0100 | |
| commit | 82851d2039f619f1b2558e06b04a9e47fceeea54 (patch) | |
| tree | ab3142289e260111c686e740b9f4214453a0a84c /docs/en/contributing.md | |
| parent | 0765840d9d0998bd09a2cf7c4fe97785c791fc9b (diff) | |
Make master the rolling release branch (#2705)
* Change default TAG in Makefile
We are going to drop the `dev` branch. The Docker tag `dev-*` are based
on this branch and so there will be no longer be generated. We must use
images based on the `master` branch (i.e. `latest`, `alpine` and `arm`).
* Remove references to dev branch in documentation
* Synchronize French documentation
Diffstat (limited to 'docs/en/contributing.md')
| -rw-r--r-- | docs/en/contributing.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/en/contributing.md b/docs/en/contributing.md index b06680e02..11c0dae40 100644 --- a/docs/en/contributing.md +++ b/docs/en/contributing.md @@ -32,7 +32,7 @@ Would you like to fix a bug? For optimum coordination between collaborators, you 1. Be sure the bug is associated with a ticket and indicate that you'll work on it. 2. [Fork the project repository](https://help.github.com/articles/fork-a-repo/). 3. [Create a new branch](https://help.github.com/articles/creating-and-deleting-branches-within-your-repository/). The name of the branch should be clear, and ideally prefixed by the related ticket id. For instance, `783-contributing-file` to fix [ticket #783](https://github.com/FreshRSS/FreshRSS/issues/783). -4. Make your changes to your fork and [send a pull request](https://help.github.com/articles/using-pull-requests/) on the **dev branch**. +4. Make your changes to your fork and [send a pull request](https://help.github.com/articles/using-pull-requests/). If you have to write code, please follow [our coding style recommendations](developers/01_First_steps.md). |
