You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Improve some badges for PTB-Raw
* doc fix for add_error_handler
* Some rendering
* Bump sphinx dependency
* Change signature annotation setting
* fix: chat_id can be string, message_id only int
* feat: add RTD link to documentation
* improving sender chat docstring (python-telegram-bot#2412)
* fix: improving sender chat docstring
also adding a note to a weird edge case
* fix: words being hard
* Add note on donations
* typo
* typo in User.get_profile_pictures docstrings
* Fix: meth, not attr for meth, not attr
* filters + inlinequery doc fix
* Bump versions, update RTD config file
* Try fix build
* Revert "fix: chat_id can be string, message_id only int"
This reverts commit ba04e5a
* Add Starry & Harshil to credits
Co-authored-by: poolitzer <[email protected]>
Co-authored-by: Harshil <[email protected]>
Copy file name to clipboardExpand all lines: .github/CONTRIBUTING.rst
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -50,6 +50,8 @@ Instructions for making a code change
50
50
51
51
The central development branch is ``master``, which should be clean and ready for release at any time. In general, all changes should be done as feature branches based off of ``master``.
52
52
53
+
If you want to do solely documentation changes, base them and PR to the branch ``doc-fixes``. This branch also has its own `RTD build`_.
54
+
53
55
Here's how to make a one-off code change.
54
56
55
57
1. **Choose a descriptive branch name.** It should be lowercase, hyphen-separated, and a noun describing the change (so, ``fuzzy-rules``, but not ``implement-fuzzy-rules``). Also, it shouldn't start with ``hotfix`` or ``release``.
@@ -250,3 +252,4 @@ break the API classes. For example:
Copy file name to clipboardExpand all lines: README.rst
+5Lines changed: 5 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -230,6 +230,11 @@ Contributing
230
230
231
231
Contributions of all sizes are welcome. Please review our `contribution guidelines <https://github.com/python-telegram-bot/python-telegram-bot/blob/master/.github/CONTRIBUTING.rst>`_ to get started. You can also help by `reporting bugs <https://github.com/python-telegram-bot/python-telegram-bot/issues/new>`_.
232
232
233
+
========
234
+
Donating
235
+
========
236
+
Occasionally we are asked if we accept donations to support the development. While we appreciate the thought, maintaining PTB is our hobby and we have almost no running costs for it. We therefore have nothing set up to accept donations. If you still want to donate, we kindly ask you to donate to another open source project/initiative of your choice instead.
Copy file name to clipboardExpand all lines: README_RAW.rst
+5Lines changed: 5 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -212,6 +212,11 @@ Contributing
212
212
213
213
Contributions of all sizes are welcome. Please review our `contribution guidelines <https://github.com/python-telegram-bot/python-telegram-bot/blob/master/.github/CONTRIBUTING.rst>`_ to get started. You can also help by `reporting bugs <https://github.com/python-telegram-bot/python-telegram-bot/issues/new>`_.
214
214
215
+
========
216
+
Donating
217
+
========
218
+
Occasionally we are asked if we accept donations to support the development. While we appreciate the thought, maintaining PTB is our hobby and we have almost no running costs for it. We therefore have nothing set up to accept donations. If you still want to donate, we kindly ask you to donate to another open source project/initiative of your choice instead.
0 commit comments