@@ -76,9 +76,9 @@ If you are proposing a feature:
76
76
Get Started!
77
77
------------
78
78
79
- Ready to contribute? Here's how to set up `rero-ils ` for local development.
79
+ Ready to contribute? Here's how to set up `` rero-ils ` ` for local development.
80
80
81
- 1. Fork the `rero/rero-ils ` repo on GitHub.
81
+ 1. Fork the `` rero/rero-ils ` ` repo on GitHub.
82
82
2. Clone your fork locally:
83
83
84
84
.. code-block :: console
@@ -105,28 +105,26 @@ Ready to contribute? Here's how to set up `rero-ils` for local development.
105
105
(code style), PEP257 (documentation), flake8 as well as build the Sphinx
106
106
documentation and run doctests.
107
107
108
- 6. Add the `.gitmessage.txt ` to your `git ` configuration:
108
+ 6. Add the `` .gitmessage.txt `` file to your `` git ` ` configuration:
109
109
110
- .. code-block::console
110
+ .. code-block :: console
111
111
112
112
# globally
113
113
$ git config --global commit.template /path/.gitmessage.txt
114
114
115
115
# locally
116
116
$ git config --local commit.template .gitmessage.txt
117
117
118
+ The ``Signed-off-by `` message is not used anymore, so you can avoid ``-s ``
119
+ parameters when committing. But of course, you can modify your own version
120
+ of the ``.gitcommit.txt `` in order to add you own ``Co-Authored-by `` message.
118
121
119
122
7. Commit your changes and push your branch to GitHub:
120
123
121
124
.. code-block :: console
122
125
123
126
$ git add .
124
127
$ git commit -s
125
- -m "component: title without verbs"
126
- -m "* NEW Adds your new feature."
127
- -m "* FIX Fixes an existing issue."
128
- -m "* BETTER Improves and existing feature."
129
- -m "* Changes something that should not be visible in release notes."
130
128
$ git push origin name-of-your-bugfix-or-feature
131
129
132
130
8. Submit a pull request through the GitHub website.
0 commit comments