Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Commit 7c37687

Browse filesBrowse files
author
Valantis Koutsoumpos
committed
Updated latest maintained version in documentation overview
1 parent c59700e commit 7c37687
Copy full SHA for 7c37687

File tree

Expand file treeCollapse file tree

1 file changed

+7
-7
lines changed
Filter options
Expand file treeCollapse file tree

1 file changed

+7
-7
lines changed

‎contributing/documentation/overview.rst

Copy file name to clipboardExpand all lines: contributing/documentation/overview.rst
+7-7Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -112,14 +112,14 @@ memorable name for the new branch (if you are fixing a reported issue, use
112112

113113
.. code-block:: terminal
114114
115-
$ git checkout -b improve_install_article upstream/2.7
115+
$ git checkout -b improve_install_article upstream/2.8
116116
117117
In this example, the name of the branch is ``improve_install_article`` and the
118-
``upstream/2.7`` value tells Git to create this branch based on the ``2.7``
118+
``upstream/2.8`` value tells Git to create this branch based on the ``2.8``
119119
branch of the ``upstream`` remote, which is the original Symfony Docs repository.
120120

121121
Fixes should always be based on the **oldest maintained branch** which contains
122-
the error. Nowadays this is the ``2.7`` branch. If you are instead documenting a
122+
the error. Nowadays this is the ``2.8`` branch. If you are instead documenting a
123123
new feature, switch to the first Symfony version that included it, e.g.
124124
``upstream/3.1``. Not sure? That's ok! Just use the ``upstream/master`` branch.
125125

@@ -155,7 +155,7 @@ changes should be applied:
155155
:align: center
156156

157157
In this example, the **base fork** should be ``symfony/symfony-docs`` and
158-
the **base** branch should be the ``2.7``, which is the branch that you selected
158+
the **base** branch should be the ``2.8``, which is the branch that you selected
159159
to base your changes on. The **head fork** should be your forked copy
160160
of ``symfony-docs`` and the **compare** branch should be ``improve_install_article``,
161161
which is the name of the branch you created and where you made your changes.
@@ -205,7 +205,7 @@ contribution to the Symfony docs:
205205
# create a new branch based on the oldest maintained version
206206
$ cd projects/symfony-docs/
207207
$ git fetch upstream
208-
$ git checkout -b my_changes upstream/2.7
208+
$ git checkout -b my_changes upstream/2.8
209209
210210
# ... do your changes
211211
@@ -288,8 +288,8 @@ into multiple branches, corresponding to the different versions of Symfony itsel
288288
The ``master`` branch holds the documentation for the development branch of
289289
the code.
290290

291-
Unless you're documenting a feature that was introduced after Symfony 2.7,
292-
your changes should always be based on the ``2.7`` branch. Documentation managers
291+
Unless you're documenting a feature that was introduced after Symfony 2.8,
292+
your changes should always be based on the ``2.8`` branch. Documentation managers
293293
will use the necessary Git-magic to also apply your changes to all the active
294294
branches of the documentation.
295295

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.