Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
weboob
Project overview
Project overview
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
175
Issues
175
List
Boards
Labels
Milestones
Merge Requests
48
Merge Requests
48
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
weboob
weboob
Commits
f90c54e4
Commit
f90c54e4
authored
Feb 19, 2018
by
Vincent A
Committed by
Phyks (Lucas Verney)
Mar 02, 2018
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
CONTRIBUTING.md: don't use reST format since the file is Markdown
parent
61701b5a
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
9 additions
and
12 deletions
+9
-12
CONTRIBUTING.md
CONTRIBUTING.md
+9
-12
No files found.
CONTRIBUTING.md
View file @
f90c54e4
...
...
@@ -14,11 +14,10 @@ a lot of duplicate work.
Write a patch
-------------
Help yourself with the
`documentation <http://docs.weboob.org/>`
_
.
Help yourself with the
[
documentation
](
http://docs.weboob.org/
)
.
Find an opened issue on
`this website
<https://git.weboob.org/weboob/devel/issues>`
_, or write your own bugfix or
feature. Then, once it is necessary, commit with::
Find an opened issue on
[
this website
](
https://git.weboob.org/weboob/devel/issues
)
,
or write your own bugfix or feature. Then, once it is necessary, commit with:
$ git commit -a
...
...
@@ -30,31 +29,29 @@ specific module, the first line of your commit message should read
Check your patch
----------------
You can run these scripts to be sure your patch doesn't break anything:
:
You can run these scripts to be sure your patch doesn't break anything:
$ tools/pyflakes.sh
$ tools/weboob_lint.sh
$ tools/run_tests.sh yourmodulename # or without yourmodulename to test everything
Perhaps you should also write or fix tests. These tests are automatically run by
`Gitlab CI <https://git.weboob.org/weboob/devel/pipelines>`
_
at each commit and merge requests.
[
Gitlab CI
](
https://git.weboob.org/weboob/devel/pipelines
)
at each commit and merge requests.
Create a merge request or send a patch
--------------------------------------
The easiest way to send your patch is to create a fork on
`the Weboob Gitla
b
<https://git.weboob.org>`
_ and create a merge request from there. This way,
the code review process is easier and continuous integration is run
The easiest way to send your patch is to create a fork on
[
the Weboo
b
Gitlab](https://git.weboob.org) and create a merge request from there.
This way,
the code review process is easier and continuous integration is run
automatically (see previous section).
If you prefer good old email patches, just use
::
$ git format-patch -n -s origin
Then, send them with this command:
:
Then, send them with this command:
$ git send-email --to=weboob@weboob.org *.patch
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment