mirror of
https://github.com/python-telegram-bot/python-telegram-bot.git
synced 2024-11-23 07:38:58 +01:00
Co-authored-by: Abubakar Alaya <ecode5814@gmail.com>
This commit is contained in:
parent
dab75fb963
commit
0eb11ff3e9
3 changed files with 3 additions and 2 deletions
|
@ -23,6 +23,7 @@ The following wonderful people contributed directly or indirectly to this projec
|
|||
|
||||
- `Abdelrahman <https://github.com/aelkheir>`_
|
||||
- `Abshar <https://github.com/abxhr>`_
|
||||
- `Abubakar Alaya <https://github.com/Ecode2>`_
|
||||
- `Alateas <https://github.com/alateas>`_
|
||||
- `Ales Dokshanin <https://github.com/alesdokshanin>`_
|
||||
- `Alexandre <https://github.com/xTudoS>`_
|
||||
|
|
|
@ -230,6 +230,6 @@ License
|
|||
-------
|
||||
|
||||
You may copy, distribute and modify the software provided that modifications are described and licensed for free under `LGPL-3 <https://www.gnu.org/licenses/lgpl-3.0.html>`_.
|
||||
Derivatives works (including modifications or anything statically linked to the library) can only be redistributed under LGPL-3, but applications that use the library don't have to be.
|
||||
Derivative works (including modifications or anything statically linked to the library) can only be redistributed under LGPL-3, but applications that use the library don't have to be.
|
||||
|
||||
.. _`GitHub releases page`: https://github.com/python-telegram-bot/python-telegram-bot/releases
|
||||
|
|
|
@ -98,7 +98,7 @@ Bots used in tests
|
|||
|
||||
If you run the tests locally, the test setup will use one of the two public bots available. Which
|
||||
bot of the two gets chosen for the test session is random. Whereas when the tests on the
|
||||
Github Actions CI are run, the test setup allocates a different, but same bot is for every combination of Python version and
|
||||
Github Actions CI are run, the test setup allocates a different, but the same bot is allocated for every combination of Python version and
|
||||
OS. The operating systems and Python versions the CI runs the tests on can be viewed in the `corresponding workflow`_.
|
||||
|
||||
|
||||
|
|
Loading…
Reference in a new issue