Commit 47e5cb07 authored by Romain Bignon's avatar Romain Bignon

rename devel.git to weboob.git

parent 64e60ac0
......@@ -16,7 +16,7 @@ Write a patch
Help yourself with the [documentation](http://docs.weboob.org/).
Find an opened issue on [this website](https://git.weboob.org/weboob/devel/issues),
Find an opened issue on [this website](https://git.weboob.org/weboob/weboob/issues),
or write your own bugfix or feature. Then, once it is necessary, commit with:
$ git commit -a
......@@ -36,7 +36,7 @@ You can run these scripts to be sure your patch doesn't break anything:
$ 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/weboob/pipelines) at each commit and merge requests.
Create a merge request or send a patch
......@@ -68,11 +68,11 @@ merge a MR.
Anyone is welcome to review and comment pending merge requests. A merge
request should in principle have at least two reviewers before getting merged.
Weboob `devel` repo should keep an history as linear as possible. Then,
merging a merge request should be done locally, with prior rebasing upon the
`master` branch and take care of using the `-ff-only` merge option. Merge
requests should **NOT** be merged through the Gitlab UI, which would result in
an extra "merge" commit.
Weboob repo should keep an history as linear as possible. Then, merging a merge
request should be done locally, with prior rebasing upon the `master` branch
and take care of using the `-ff-only` merge option. Merge requests should
**NOT** be merged through the Gitlab UI, which would result in an extra "merge"
commit.
Getting your contribution accepted
......
<h3>Other resources</h3>
<ul>
<li><a href="http://weboob.org/">Official website</a></li>
<li><a href="https://git.weboob.org/weboob/devel/issues">Bug Tracker</a></li>
<li><a href="https://git.weboob.org/weboob/weboob/issues">Bug Tracker</a></li>
<li><a href="https://symlink.me/projects/weboob/files">Download stable version</a></li>
</ul>
......@@ -9,7 +9,7 @@ Write a patch
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.
Find an opened issue on `this website <https://git.weboob.org/weboob/weboob/issues>`_, or write your own bugfix or feature.
Then, once it is necessary, commit with::
$ git commit -a
......@@ -31,7 +31,7 @@ To aid in verifying Python 3 compatibility, also run::
$ tools/run_tests.sh -3 yourmodulename
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/weboob/pipelines>`_ at each commit and merge requests.
Create a merge request or send a patch
--------------------------------------
......
......@@ -8,7 +8,7 @@ Git installation
Clone a git repository with this command::
$ git clone https://git.weboob.org/weboob/devel.git
$ git clone https://git.weboob.org/weboob/weboob.git
We don't want to install Weboob on the whole system, so we create local directories where
we will put symbolic links to sources::
......
......@@ -21,7 +21,7 @@ Then, it run every method which name starts with ``test_``.
.. note::
Some environment variables are available, to use specific backend file or send the test results. Refer to `the
comments in the script <https://git.weboob.org/weboob/devel/blob/master/tools/run_tests.sh#L4-8>`_ for more infos on this.
comments in the script <https://git.weboob.org/weboob/weboob/blob/master/tools/run_tests.sh#L4-8>`_ for more infos on this.
If a module name is passed as argument, only this module will be tested. For example, to only run ``lutim`` tests::
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment