Documentation Improvements (#3029)

Co-authored-by: Hinrich Mahler <22366557+Bibo-Joshi@users.noreply.github.com>

Co-authored-by: Sukka <isukkaw@gmail.com>

.github/ISSUE_TEMPLATE/question.yml

@@ -9,9 +9,9 @@ body:
       value: |
         Hey there, you have a question? We are happy to answer. Please make sure no similar question was opened already.
 
-        To make it easier for us to help you, please read this [article](https://git.io/JURJO).
+        To make it easier for us to help you, please read this [article](https://github.com/python-telegram-bot/python-telegram-bot/wiki/Ask-Right).
 
-        Please mind that there is also a users' [Telegram group](https://t.me/pythontelegrambotgroup) for questions about the library. Questions asked there might be answered quicker than here. Moreover, [GitHub Discussions](https://git.io/JG3rk) offer a slightly better format to discuss usage questions.
+        Please mind that there is also a users' [Telegram group](https://t.me/pythontelegrambotgroup) for questions about the library. Questions asked there might be answered quicker than here. Moreover, [GitHub Discussions](https://github.com/python-telegram-bot/python-telegram-bot/discussions) offer a slightly better format to discuss usage questions.
 
   - type: textarea
     id: issue-faced

CHANGES.rst

@@ -895,7 +895,7 @@ Expect minor releases soon (mainly complete Bot API 4.4 support)
 - Error Handler now handles all types of exceptions (`#1485`_)
 - Return UTC from from_timestamp() (`#1485`_)
 
-**See the wiki page at https://git.io/fxJuV for a detailed guide on how to migrate from version 11 to version 12.**
+**See the wiki page at https://github.com/python-telegram-bot/python-telegram-bot/wiki/Transition-guide-to-Version-12.0 for a detailed guide on how to migrate from version 11 to version 12.**
 
 Context based callbacks (`#1100`_)
 ----------------------------------
@@ -1100,7 +1100,7 @@ Non Bot API 4.0 changes:
 .. _`#1172`: https://github.com/python-telegram-bot/python-telegram-bot/pull/1172
 .. _`#1179`: https://github.com/python-telegram-bot/python-telegram-bot/pull/1179
 .. _`#1184`: https://github.com/python-telegram-bot/python-telegram-bot/pull/1184
-.. _`our telegram passport wiki page`: https://git.io/fAvYd
+.. _`our telegram passport wiki page`: https://github.com/python-telegram-bot/python-telegram-bot/wiki/Telegram-Passport
 
 Version 10.1.0
 ==============

README.rst

@@ -100,7 +100,7 @@ In addition to the pure API implementation, this library features a number of hi
 make the development of bots easy and straightforward. These classes are contained in the
 ``telegram.ext`` submodule.
 
-A pure API implementation *without* ``telegram.ext`` is available as the standalone package ``python-telegram-bot-raw``.  `See here for details. <https://github.com/python-telegram-bot/python-telegram-bot/blob/master/README_RAW.rst>`_
+A pure API implementation *without* ``telegram.ext`` is available as the standalone package ``python-telegram-bot-raw``.  `See here for details. <https://github.com/python-telegram-bot/python-telegram-bot/blob/v13.x/README_RAW.rst>`_
 
 ----
 Note
@@ -172,7 +172,7 @@ look at ``echobot.py``, it is the de facto base for most of the bots out there.
 the code for these examples are released to the public domain, so you can start by grabbing the
 code and building on top of it.
 
-Visit `this page <https://github.com/python-telegram-bot/python-telegram-bot/blob/master/examples/README.md>`_ to discover the official examples or look at the examples on the `wiki <https://github.com/python-telegram-bot/python-telegram-bot/wiki/Examples>`_ to see other bots the community has built.
+Visit `this page <https://github.com/python-telegram-bot/python-telegram-bot/blob/v13.x/examples/README.md>`_ to discover the official examples or look at the examples on the `wiki <https://github.com/python-telegram-bot/python-telegram-bot/wiki/Examples>`_ to see other bots the community has built.
 
 -------
 Logging
@@ -227,7 +227,7 @@ You can get help in several ways:
 Contributing
 ============
 
-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>`_.
+Contributions of all sizes are welcome. Please review our `contribution guidelines <https://github.com/python-telegram-bot/python-telegram-bot/blob/v13.x/.github/CONTRIBUTING.rst>`_ to get started. You can also help by `reporting bugs <https://github.com/python-telegram-bot/python-telegram-bot/issues/new>`_.
 
 ========
 Donating

README_RAW.rst

@@ -208,7 +208,7 @@ You can get help in several ways:
 Contributing
 ============
 
-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>`_.
+Contributions of all sizes are welcome. Please review our `contribution guidelines <https://github.com/python-telegram-bot/python-telegram-bot/blob/v13.x/.github/CONTRIBUTING.rst>`_ to get started. You can also help by `reporting bugs <https://github.com/python-telegram-bot/python-telegram-bot/issues/new>`_.
 
 ========
 Donating

docs/source/_static/dark.css

@@ -2,7 +2,7 @@
     /*
     Generated by https://darkreader.org
     Instructions: Install the extension on a Chromium-based browser
-    Then do this to export the CSS: https://git.io/JOM6t and drop it here
+    Then do this to export the CSS: https://github.com/darkreader/darkreader/issues/604#issuecomment-661107893 and drop it here
     Some color values where manually changed - just search for "/*" in this file and insert them in the new css
     */
     /* User-Agent Style */

examples/README.md

@@ -2,60 +2,60 @@
 
 In this folder are small examples to show what a bot written with `python-telegram-bot` looks like. Some bots focus on one specific aspect of the Telegram Bot API while others focus on one of the mechanics of this library. Except for the [`rawapibot.py`](#pure-api) example, they all use the high-level framework this library provides with the [`telegram.ext`](https://python-telegram-bot.readthedocs.io/en/latest/telegram.ext.html) submodule.
 
-All examples are licensed under the [CC0 License](https://github.com/python-telegram-bot/python-telegram-bot/blob/master/examples/LICENSE.txt) and are therefore fully dedicated to the public domain. You can use them as the base for your own bots without worrying about copyrights.
+All examples are licensed under the [CC0 License](https://github.com/python-telegram-bot/python-telegram-bot/blob/v13.x/examples/LICENSE.txt) and are therefore fully dedicated to the public domain. You can use them as the base for your own bots without worrying about copyrights.
 
 Do note that we ignore one pythonic convention. Best practice would dictate, in many handler callbacks function signatures, to replace the argument `context` with an underscore, since `context` is an unused local variable in those callbacks. However, since these are examples and not having a name for that argument confuses beginners, we decided to have it present.
 
-### [`echobot.py`](https://github.com/python-telegram-bot/python-telegram-bot/blob/master/examples/echobot.py) 
+### [`echobot.py`](https://github.com/python-telegram-bot/python-telegram-bot/blob/v13.x/examples/echobot.py) 
 This is probably the base for most of the bots made with `python-telegram-bot`. It simply replies to each text message with a message that contains the same text.
 
-### [`timerbot.py`](https://github.com/python-telegram-bot/python-telegram-bot/blob/master/examples/timerbot.py) 
+### [`timerbot.py`](https://github.com/python-telegram-bot/python-telegram-bot/blob/v13.x/examples/timerbot.py) 
 This bot uses the [`JobQueue`](https://python-telegram-bot.readthedocs.io/en/latest/telegram.ext.jobqueue.html) class to send timed messages. The user sets a timer by using `/set` command with a specific time, for example `/set 30`. The bot then sets up a job to send a message to that user after 30 seconds. The user can also cancel the timer by sending `/unset`. To learn more about the `JobQueue`, read [this wiki article](https://github.com/python-telegram-bot/python-telegram-bot/wiki/Extensions-%E2%80%93-JobQueue).
 
-### [`conversationbot.py`](https://github.com/python-telegram-bot/python-telegram-bot/blob/master/examples/conversationbot.py)
+### [`conversationbot.py`](https://github.com/python-telegram-bot/python-telegram-bot/blob/v13.x/examples/conversationbot.py)
-A common task for a bot is to ask information from the user. In v5.0 of this library, we introduced the [`ConversationHandler`](https://python-telegram-bot.readthedocs.io/en/latest/telegram.ext.conversationhandler.html) for that exact purpose. This example uses it to retrieve user-information in a conversation-like style. To get a better understanding, take a look at the [state diagram](https://github.com/python-telegram-bot/python-telegram-bot/blob/master/examples/conversationbot.png).
+A common task for a bot is to ask information from the user. In v5.0 of this library, we introduced the [`ConversationHandler`](https://python-telegram-bot.readthedocs.io/en/latest/telegram.ext.conversationhandler.html) for that exact purpose. This example uses it to retrieve user-information in a conversation-like style. To get a better understanding, take a look at the [state diagram](https://github.com/python-telegram-bot/python-telegram-bot/blob/v13.x/examples/conversationbot.png).
 
-### [`conversationbot2.py`](https://github.com/python-telegram-bot/python-telegram-bot/blob/master/examples/conversationbot2.py)
+### [`conversationbot2.py`](https://github.com/python-telegram-bot/python-telegram-bot/blob/v13.x/examples/conversationbot2.py)
-A more complex example of a bot that uses the `ConversationHandler`. It is also more confusing. Good thing there is a [fancy state diagram](https://github.com/python-telegram-bot/python-telegram-bot/blob/master/examples/conversationbot2.png) for this one, too!
+A more complex example of a bot that uses the `ConversationHandler`. It is also more confusing. Good thing there is a [fancy state diagram](https://github.com/python-telegram-bot/python-telegram-bot/blob/v13.x/examples/conversationbot2.png) for this one, too!
 
-### [`nestedconversationbot.py`](https://github.com/python-telegram-bot/python-telegram-bot/blob/master/examples/nestedconversationbot.py)
+### [`nestedconversationbot.py`](https://github.com/python-telegram-bot/python-telegram-bot/blob/v13.x/examples/nestedconversationbot.py)
-A even more complex example of a bot that uses the nested `ConversationHandler`s. While it's certainly not that complex that you couldn't built it without nested `ConversationHanldler`s, it gives a good impression on how to work with them. Of course, there is a [fancy state diagram](https://github.com/python-telegram-bot/python-telegram-bot/blob/master/examples/nestedconversationbot.png) for this example, too!
+A even more complex example of a bot that uses the nested `ConversationHandler`s. While it's certainly not that complex that you couldn't built it without nested `ConversationHanldler`s, it gives a good impression on how to work with them. Of course, there is a [fancy state diagram](https://github.com/python-telegram-bot/python-telegram-bot/blob/v13.x/examples/nestedconversationbot.png) for this example, too!
 
-### [`persistentconversationbot.py`](https://github.com/python-telegram-bot/python-telegram-bot/blob/master/examples/persistentconversationbot.py)
+### [`persistentconversationbot.py`](https://github.com/python-telegram-bot/python-telegram-bot/blob/v13.x/examples/persistentconversationbot.py)
 A basic example of a bot store conversation state and user_data over multiple restarts.
 
-### [`inlinekeyboard.py`](https://github.com/python-telegram-bot/python-telegram-bot/blob/master/examples/inlinekeyboard.py)
+### [`inlinekeyboard.py`](https://github.com/python-telegram-bot/python-telegram-bot/blob/v13.x/examples/inlinekeyboard.py)
-This example sheds some light on inline keyboards, callback queries and message editing. A wikipedia site explaining this examples lives at https://git.io/JOmFw.
+This example sheds some light on inline keyboards, callback queries and message editing. A wikipedia site explaining this examples lives at https://github.com/python-telegram-bot/python-telegram-bot/wiki/InlineKeyboard-Example.
 
-### [`inlinekeyboard2.py`](https://github.com/python-telegram-bot/python-telegram-bot/blob/master/examples/inlinekeyboard2.py)
+### [`inlinekeyboard2.py`](https://github.com/python-telegram-bot/python-telegram-bot/blob/v13.x/examples/inlinekeyboard2.py)
 A more complex example about inline keyboards, callback queries and message editing. This example showcases how an interactive menu could be build using inline keyboards.
 
-### [`deeplinking.py`](https://github.com/python-telegram-bot/python-telegram-bot/blob/master/examples/deeplinking.py)
+### [`deeplinking.py`](https://github.com/python-telegram-bot/python-telegram-bot/blob/v13.x/examples/deeplinking.py)
 A basic example on how to use deeplinking with inline keyboards.
 
-### [`inlinebot.py`](https://github.com/python-telegram-bot/python-telegram-bot/blob/master/examples/inlinebot.py)
+### [`inlinebot.py`](https://github.com/python-telegram-bot/python-telegram-bot/blob/v13.x/examples/inlinebot.py)
 A basic example of an [inline bot](https://core.telegram.org/bots/inline). Don't forget to enable inline mode with [@BotFather](https://telegram.me/BotFather).
 
-### [`pollbot.py`](https://github.com/python-telegram-bot/python-telegram-bot/blob/master/examples/pollbot.py)
+### [`pollbot.py`](https://github.com/python-telegram-bot/python-telegram-bot/blob/v13.x/examples/pollbot.py)
 This example sheds some light on polls, poll answers and the corresponding handlers.
 
-### [`passportbot.py`](https://github.com/python-telegram-bot/python-telegram-bot/blob/master/examples/passportbot.py)
+### [`passportbot.py`](https://github.com/python-telegram-bot/python-telegram-bot/blob/v13.x/examples/passportbot.py)
-A basic example of a bot that can accept passports. Use in combination with [`passportbot.html`](https://github.com/python-telegram-bot/python-telegram-bot/blob/master/examples/passportbot.html). Don't forget to enable and configure payments with [@BotFather](https://telegram.me/BotFather). Check out this [guide](https://git.io/fAvYd) on Telegram passports in PTB.
+A basic example of a bot that can accept passports. Use in combination with [`passportbot.html`](https://github.com/python-telegram-bot/python-telegram-bot/blob/v13.x/examples/passportbot.html). Don't forget to enable and configure payments with [@BotFather](https://telegram.me/BotFather). Check out this [guide](https://github.com/python-telegram-bot/python-telegram-bot/wiki/Telegram-Passport) on Telegram passports in PTB.
 
-### [`paymentbot.py`](https://github.com/python-telegram-bot/python-telegram-bot/blob/master/examples/paymentbot.py)
+### [`paymentbot.py`](https://github.com/python-telegram-bot/python-telegram-bot/blob/v13.x/examples/paymentbot.py)
 A basic example of a bot that can accept payments. Don't forget to enable and configure payments with [@BotFather](https://telegram.me/BotFather).
 
-### [`errorhandlerbot.py`](https://github.com/python-telegram-bot/python-telegram-bot/blob/master/examples/errorhandlerbot.py)
+### [`errorhandlerbot.py`](https://github.com/python-telegram-bot/python-telegram-bot/blob/v13.x/examples/errorhandlerbot.py)
 A basic example on how to set up a custom error handler.
 
-### [`chatmemberbot.py`](https://github.com/python-telegram-bot/python-telegram-bot/blob/master/examples/chatmemberbot.py)
+### [`chatmemberbot.py`](https://github.com/python-telegram-bot/python-telegram-bot/blob/v13.x/examples/chatmemberbot.py)
 A basic example on how `(my_)chat_member` updates can be used.
 
-### [`contexttypesbot.py`](https://github.com/python-telegram-bot/python-telegram-bot/blob/master/examples/contexttypesbot.py)
+### [`contexttypesbot.py`](https://github.com/python-telegram-bot/python-telegram-bot/blob/v13.x/examples/contexttypesbot.py)
 This example showcases how `telegram.ext.ContextTypes` can be used to customize the `context` argument of handler and job callbacks.
 
-### [`arbitrarycallbackdatabot.py`](https://github.com/python-telegram-bot/python-telegram-bot/blob/master/examples/arbitrarycallbackdatabot.py)
+### [`arbitrarycallbackdatabot.py`](https://github.com/python-telegram-bot/python-telegram-bot/blob/v13.x/examples/arbitrarycallbackdatabot.py)
 This example showcases how PTBs "arbitrary callback data" feature can be used.
 
 ## Pure API
-The [`rawapibot.py`](https://github.com/python-telegram-bot/python-telegram-bot/blob/master/examples/rawapibot.py) example uses only the pure, "bare-metal" API wrapper.
+The [`rawapibot.py`](https://github.com/python-telegram-bot/python-telegram-bot/blob/v13.x/examples/rawapibot.py) example uses only the pure, "bare-metal" API wrapper.

examples/arbitrarycallbackdatabot.py

@@ -4,7 +4,8 @@
 
 """This example showcases how PTBs "arbitrary callback data" feature can be used.
 
-For detailed info on arbitrary callback data, see the wiki page at https://git.io/JGBDI
+For detailed info on arbitrary callback data, see the wiki page at
+https://github.com/python-telegram-bot/python-telegram-bot/wiki/Arbitrary-callback_data
 """
 import logging
 from typing import List, Tuple, cast

examples/inlinekeyboard.py

@@ -4,7 +4,7 @@
 
 """
 Basic example for a bot that uses inline keyboards. For an in-depth explanation, check out
- https://git.io/JOmFw.
+ https://github.com/python-telegram-bot/python-telegram-bot/wiki/InlineKeyboard-Example.
 """
 import logging
 

examples/passportbot.py

@@ -7,7 +7,8 @@ Simple Bot to print/download all incoming passport data
 
 See https://telegram.org/blog/passport for info about what telegram passport is.
 
-See https://git.io/fAvYd for how to use Telegram Passport properly with python-telegram-bot.
+See https://github.com/python-telegram-bot/python-telegram-bot/wiki/Telegram-Passport
+for how to use Telegram Passport properly with python-telegram-bot.
 
 """
 import logging

setup.py

@@ -65,7 +65,7 @@ def get_setup_kwargs(raw=False):
             author_email='devs@python-telegram-bot.org',
             license='LGPLv3',
             url='https://python-telegram-bot.org/',
-            # Keywords supported by PyPI can be found at https://git.io/JtLIZ
+            # Keywords supported by PyPI can be found at https://github.com/pypa/warehouse/blob/aafc5185e57e67d43487ce4faa95913dd4573e14/warehouse/templates/packaging/detail.html#L20-L58
             project_urls={
                 "Documentation": "https://python-telegram-bot.readthedocs.io",
                 "Bug Tracker": "https://github.com/python-telegram-bot/python-telegram-bot/issues",

telegram/dice.py

@@ -50,8 +50,9 @@ class Dice(TelegramObject):
         Telegram.
 
         If :attr:`emoji` is "🎰", each value corresponds to a unique combination of symbols, which
-        can be found at our `wiki <https://git.io/JkeC6>`_. However, this behaviour is undocumented
+        can be found at our `wiki <https://github.com/python-telegram-bot/python-telegram-bot/\
-        and might be changed by Telegram.
+        wiki/Code-snippets#map-a-slot-machine-dice-value-to-the-corresponding-symbols>`_.
+        However, this behaviour is undocumented and might be changed by Telegram.
 
     Args:
         value (:obj:`int`): Value of the dice. 1-6 for dice, darts and bowling balls, 1-5 for

telegram/ext/callbackcontext.py

@@ -139,7 +139,9 @@ class CallbackContext(Generic[UD, CD, BD]):
     @bot_data.setter
     def bot_data(self, value: object) -> NoReturn:
         raise AttributeError(
-            "You can not assign a new value to bot_data, see https://git.io/Jt6ic"
+            "You can not assign a new value to bot_data, "
+            "see https://github.com/python-telegram-bot/python-telegram-bot/wiki/Storing-bot%2C"
+            "-user-and-chat-related-data "
         )
 
     @property
@@ -160,7 +162,9 @@ class CallbackContext(Generic[UD, CD, BD]):
     @chat_data.setter
     def chat_data(self, value: object) -> NoReturn:
         raise AttributeError(
-            "You can not assign a new value to chat_data, see https://git.io/Jt6ic"
+            "You can not assign a new value to chat_data, "
+            "see https://github.com/python-telegram-bot/python-telegram-bot/wiki/Storing-bot%2C"
+            "-user-and-chat-related-data "
         )
 
     @property
@@ -175,7 +179,9 @@ class CallbackContext(Generic[UD, CD, BD]):
     @user_data.setter
     def user_data(self, value: object) -> NoReturn:
         raise AttributeError(
-            "You can not assign a new value to user_data, see https://git.io/Jt6ic"
+            "You can not assign a new value to user_data, "
+            "see https://github.com/python-telegram-bot/python-telegram-bot/wiki/Storing-bot%2C"
+            "-user-and-chat-related-data "
         )
 
     def refresh_data(self) -> None:

telegram/ext/callbackqueryhandler.py

@@ -55,7 +55,8 @@ class CallbackQueryHandler(Handler[Update, CCT]):
           user or in the same chat, it will be the same ``dict``.
 
           Note that this is DEPRECATED, and you should use context based callbacks. See
-          https://git.io/fxJuV for more info.
+          https://github.com/python-telegram-bot/python-telegram-bot/wiki\
+          /Transition-guide-to-Version-12.0 for more info.
         * If your bot allows arbitrary objects as ``callback_data``, it may happen that the
           original ``callback_data`` for the incoming :class:`telegram.CallbackQuery`` can not be
           found. This is the case when either a malicious client tempered with the

telegram/ext/chatjoinrequesthandler.py

@@ -35,7 +35,8 @@ class ChatJoinRequestHandler(Handler[Update, CCT]):
         or in the same chat, it will be the same ``dict``.
 
         Note that this is DEPRECATED, and you should use context based callbacks. See
-        https://git.io/fxJuV for more info.
+        https://github.com/python-telegram-bot/python-telegram-bot/wiki\
+        /Transition-guide-to-Version-12.0 for more info.
 
     Warning:
         When setting ``run_async`` to :obj:`True`, you cannot rely on adding custom

telegram/ext/chatmemberhandler.py

@@ -39,7 +39,8 @@ class ChatMemberHandler(Handler[Update, CCT]):
         or in the same chat, it will be the same ``dict``.
 
         Note that this is DEPRECATED, and you should use context based callbacks. See
-        https://git.io/fxJuV for more info.
+        https://github.com/python-telegram-bot/python-telegram-bot/wiki\
+        /Transition-guide-to-Version-12.0 for more info.
 
     Warning:
         When setting ``run_async`` to :obj:`True`, you cannot rely on adding custom

telegram/ext/choseninlineresulthandler.py

@@ -42,7 +42,8 @@ class ChosenInlineResultHandler(Handler[Update, CCT]):
         or in the same chat, it will be the same ``dict``.
 
         Note that this is DEPRECATED, and you should use context based callbacks. See
-        https://git.io/fxJuV for more info.
+        https://github.com/python-telegram-bot/python-telegram-bot/wiki\
+        /Transition-guide-to-Version-12.0 for more info.
 
     Warning:
         When setting ``run_async`` to :obj:`True`, you cannot rely on adding custom

telegram/ext/commandhandler.py

@@ -55,7 +55,8 @@ class CommandHandler(Handler[Update, CCT]):
           user or in the same chat, it will be the same :obj:`dict`.
 
           Note that this is DEPRECATED, and you should use context based callbacks. See
-          https://git.io/fxJuV for more info.
+          https://github.com/python-telegram-bot/python-telegram-bot/wiki\
+          /Transition-guide-to-Version-12.0 for more info.
 
     Warning:
         When setting ``run_async`` to :obj:`True`, you cannot rely on adding custom
@@ -169,7 +170,9 @@ class CommandHandler(Handler[Update, CCT]):
 
         if allow_edited is not None:
             warnings.warn(
-                'allow_edited is deprecated. See https://git.io/fxJuV for more info',
+                'allow_edited is deprecated. See '
+                'https://github.com/python-telegram-bot/python-telegram-bot/wiki/Transition'
+                '-guide-to-Version-12.0 for more info',
                 TelegramDeprecationWarning,
                 stacklevel=2,
             )
@@ -288,7 +291,8 @@ class PrefixHandler(CommandHandler):
           user or in the same chat, it will be the same :obj:`dict`.
 
           Note that this is DEPRECATED, and you should use context based callbacks. See
-          https://git.io/fxJuV for more info.
+          https://github.com/python-telegram-bot/python-telegram-bot/wiki\
+        /Transition-guide-to-Version-12.0 for more info.
 
     Warning:
         When setting ``run_async`` to :obj:`True`, you cannot rely on adding custom

telegram/ext/contexttypes.py

@@ -50,7 +50,8 @@ class ContextTypes(Generic[CCT, UD, CD, BD]):
 
     __slots__ = ('_context', '_bot_data', '_chat_data', '_user_data')
 
-    # overload signatures generated with https://git.io/JtJPj
+    # overload signatures generated with
+    # https://gist.github.com/Bibo-Joshi/399382cda537fb01bd86b13c3d03a956
 
     @overload
     def __init__(

telegram/ext/conversationhandler.py

@@ -79,7 +79,8 @@ class ConversationHandler(Handler[Update, CCT]):
 
         Finally, ``ConversationHandler``, does *not* handle (edited) channel posts.
 
-    .. _`FAQ`: https://git.io/JtcyU
+    .. _`FAQ`: https://github.com/python-telegram-bot/python-telegram-bot/wiki\
+        /Frequently-Asked-Questions#what-do-the-per_-settings-in-conversationhandler-do
 
     The first collection, a ``list`` named :attr:`entry_points`, is used to initiate the
     conversation, for example with a :class:`telegram.ext.CommandHandler` or
@@ -119,7 +120,7 @@ class ConversationHandler(Handler[Update, CCT]):
         :attr:`END` to end the *parent* conversation from within the nested one. For an example on
         nested :class:`ConversationHandler` s, see our `examples`_.
 
-    .. _`examples`: https://github.com/python-telegram-bot/python-telegram-bot/blob/master/examples
+    .. _`examples`: https://github.com/python-telegram-bot/python-telegram-bot/blob/v13.x/examples
 
     Args:
         entry_points (List[:class:`telegram.ext.Handler`]): A list of ``Handler`` objects that can

telegram/ext/dispatcher.py

@@ -241,7 +241,9 @@ class Dispatcher(Generic[CCT, UD, CD, BD]):
 
         if not use_context:
             warnings.warn(
-                'Old Handler API is deprecated - see https://git.io/fxJuV for details',
+                'Old Handler API is deprecated - see '
+                'https://github.com/python-telegram-bot/python-telegram-bot/wiki/Transition'
+                '-guide-to-Version-12.0 for details',
                 TelegramDeprecationWarning,
                 stacklevel=3,
             )
@@ -763,7 +765,8 @@ class Dispatcher(Generic[CCT, UD, CD, BD]):
                 asynchronously using :meth:`run_async`. Defaults to :obj:`False`.
 
         Note:
-            See https://git.io/fxJuV for more info about switching to context based API.
+            See https://github.com/python-telegram-bot/python-telegram-bot/wiki\
+            /Transition-guide-to-Version-12.0 for more info about switching to context based API.
         """
         if callback in self.error_handlers:
             self.logger.debug('The callback is already registered as an error handler. Ignoring.')

telegram/ext/extbot.py

@@ -62,7 +62,9 @@ class ExtBot(telegram.bot.Bot):
         arbitrary_callback_data (:obj:`bool` | :obj:`int`, optional): Whether to
             allow arbitrary objects as callback data for :class:`telegram.InlineKeyboardButton`.
             Pass an integer to specify the maximum number of objects cached in memory. For more
-            details, please see our `wiki <https://git.io/JGBDI>`_. Defaults to :obj:`False`.
+            details, please see our `wiki <https://github.com/python-telegram-bot/\
+            python-telegram-bot/wiki/Arbitrary-callback_data>`_.
+            Defaults to :obj:`False`.
 
     Attributes:
         arbitrary_callback_data (:obj:`bool` | :obj:`int`): Whether this bot instance

telegram/ext/handler.py

@@ -45,7 +45,8 @@ class Handler(Generic[UT, CCT], ABC):
         or in the same chat, it will be the same ``dict``.
 
         Note that this is DEPRECATED, and you should use context based callbacks. See
-        https://git.io/fxJuV for more info.
+        https://github.com/python-telegram-bot/python-telegram-bot/wiki\
+        /Transition-guide-to-Version-12.0 for more info.
 
     Warning:
         When setting ``run_async`` to :obj:`True`, you cannot rely on adding custom
@@ -232,7 +233,8 @@ class Handler(Generic[UT, CCT], ABC):
         it should subclass this method, but remember to call this super method.
 
         DEPRECATED: This method is being replaced by new context based callbacks. Please see
-        https://git.io/fxJuV for more info.
+        https://github.com/python-telegram-bot/python-telegram-bot/wiki\
+        /Transition-guide-to-Version-12.0 for more info.
 
         Args:
             dispatcher (:class:`telegram.ext.Dispatcher`): The dispatcher.

telegram/ext/inlinequeryhandler.py

@@ -55,7 +55,8 @@ class InlineQueryHandler(Handler[Update, CCT]):
         or in the same chat, it will be the same ``dict``.
 
         Note that this is DEPRECATED, and you should use context based callbacks. See
-        https://git.io/fxJuV for more info.
+        https://github.com/python-telegram-bot/python-telegram-bot/wiki\
+        /Transition-guide-to-Version-12.0 for more info.
 
     Warning:
         * When setting ``run_async`` to :obj:`True`, you cannot rely on adding custom

telegram/ext/messagehandler.py

@@ -45,7 +45,8 @@ class MessageHandler(Handler[Update, CCT]):
         or in the same chat, it will be the same ``dict``.
 
         Note that this is DEPRECATED, and you should use context based callbacks. See
-        https://git.io/fxJuV for more info.
+        https://github.com/python-telegram-bot/python-telegram-bot/wiki\
+        /Transition-guide-to-Version-12.0 for more info.
 
     Warning:
         When setting ``run_async`` to :obj:`True`, you cannot rely on adding custom
@@ -155,7 +156,9 @@ class MessageHandler(Handler[Update, CCT]):
             self.filters = Filters.update
         if message_updates is not None:
             warnings.warn(
-                'message_updates is deprecated. See https://git.io/fxJuV for more info',
+                'message_updates is deprecated. See '
+                'https://github.com/python-telegram-bot/python-telegram-bot/wiki/Transition'
+                '-guide-to-Version-12.0 for more info',
                 TelegramDeprecationWarning,
                 stacklevel=2,
             )
@@ -164,7 +167,10 @@ class MessageHandler(Handler[Update, CCT]):
 
         if channel_post_updates is not None:
             warnings.warn(
-                'channel_post_updates is deprecated. See https://git.io/fxJuV ' 'for more info',
+                'channel_post_updates is deprecated. See '
+                'https://github.com/python-telegram-bot/python-telegram-bot/wiki/Transition'
+                '-guide-to-Version-12.0 '
+                'for more info',
                 TelegramDeprecationWarning,
                 stacklevel=2,
             )
@@ -173,7 +179,9 @@ class MessageHandler(Handler[Update, CCT]):
 
         if edited_updates is not None:
             warnings.warn(
-                'edited_updates is deprecated. See https://git.io/fxJuV for more info',
+                'edited_updates is deprecated. See '
+                'https://github.com/python-telegram-bot/python-telegram-bot/wiki/Transition'
+                '-guide-to-Version-12.0 for more info',
                 TelegramDeprecationWarning,
                 stacklevel=2,
             )

telegram/ext/messagequeue.py

@@ -50,7 +50,8 @@ class DelayQueue(threading.Thread):
 
     .. deprecated:: 13.3
        :class:`telegram.ext.DelayQueue` in its current form is deprecated and will be reinvented
-       in a future release. See `this thread <https://git.io/JtDbF>`_ for a list of known bugs.
+       in a future release. See `this thread <https://github.com/python-telegram-bot/\
+       python-telegram-bot/issues/2139>`_ for a list of known bugs.
 
     Args:
         queue (:obj:`Queue`, optional): Used to pass callbacks to thread. Creates ``Queue``
@@ -92,7 +93,8 @@ class DelayQueue(threading.Thread):
     ):
         warnings.warn(
             'DelayQueue in its current form is deprecated and will be reinvented in a future '
-            'release. See https://git.io/JtDbF for a list of known bugs.',
+            'release. See https://github.com/python-telegram-bot/python-telegram-bot/issues/2139 '
+            'for a list of known bugs.',
             category=TelegramDeprecationWarning,
         )
 
@@ -194,7 +196,8 @@ class MessageQueue:
 
     .. deprecated:: 13.3
        :class:`telegram.ext.MessageQueue` in its current form is deprecated and will be reinvented
-       in a future release. See `this thread <https://git.io/JtDbF>`_ for a list of known bugs.
+       in a future release. See `this thread <https://github.com/python-telegram-bot/\
+       python-telegram-bot/issues/2139>`_ for a list of known bugs.
 
     Args:
         all_burst_limit (:obj:`int`, optional): Number of maximum *all-type* callbacks to process
@@ -226,7 +229,8 @@ class MessageQueue:
     ):
         warnings.warn(
             'MessageQueue in its current form is deprecated and will be reinvented in a future '
-            'release. See https://git.io/JtDbF for a list of known bugs.',
+            'release. See https://github.com/python-telegram-bot/python-telegram-bot/issues/2139 '
+            'for a list of known bugs.',
             category=TelegramDeprecationWarning,
         )
 

telegram/ext/pollanswerhandler.py

@@ -35,7 +35,8 @@ class PollAnswerHandler(Handler[Update, CCT]):
         or in the same chat, it will be the same ``dict``.
 
         Note that this is DEPRECATED, and you should use context based callbacks. See
-        https://git.io/fxJuV for more info.
+        https://github.com/python-telegram-bot/python-telegram-bot/wiki\
+        /Transition-guide-to-Version-12.0 for more info.
 
     Warning:
         When setting ``run_async`` to :obj:`True`, you cannot rely on adding custom

telegram/ext/pollhandler.py

@@ -35,7 +35,8 @@ class PollHandler(Handler[Update, CCT]):
         or in the same chat, it will be the same ``dict``.
 
         Note that this is DEPRECATED, and you should use context based callbacks. See
-        https://git.io/fxJuV for more info.
+        https://github.com/python-telegram-bot/python-telegram-bot/wiki\
+        /Transition-guide-to-Version-12.0 for more info.
 
     Warning:
         When setting ``run_async`` to :obj:`True`, you cannot rely on adding custom

telegram/ext/precheckoutqueryhandler.py

@@ -35,7 +35,8 @@ class PreCheckoutQueryHandler(Handler[Update, CCT]):
         or in the same chat, it will be the same ``dict``.
 
         Note that this is DEPRECATED, and you should use context based callbacks. See
-        https://git.io/fxJuV for more info.
+        https://github.com/python-telegram-bot/python-telegram-bot/wiki\
+        /Transition-guide-to-Version-12.0 for more info.
 
     Warning:
         When setting ``run_async`` to :obj:`True`, you cannot rely on adding custom

telegram/ext/regexhandler.py

@@ -128,7 +128,9 @@ class RegexHandler(MessageHandler):
         run_async: Union[bool, DefaultValue] = DEFAULT_FALSE,
     ):
         warnings.warn(
-            'RegexHandler is deprecated. See https://git.io/fxJuV for more info',
+            'RegexHandler is deprecated. See '
+            'https://github.com/python-telegram-bot/python-telegram-bot/wiki/Transition-guide-to'
+            '-Version-12.0 for more info',
             TelegramDeprecationWarning,
             stacklevel=2,
         )

telegram/ext/shippingqueryhandler.py

@@ -34,7 +34,8 @@ class ShippingQueryHandler(Handler[Update, CCT]):
         or in the same chat, it will be the same ``dict``.
 
         Note that this is DEPRECATED, and you should use context based callbacks. See
-        https://git.io/fxJuV for more info.
+        https://github.com/python-telegram-bot/python-telegram-bot/wiki\
+        /Transition-guide-to-Version-12.0 for more info.
 
     Warning:
         When setting ``run_async`` to :obj:`True`, you cannot rely on adding custom

tests/test_commandhandler.py

@@ -204,7 +204,11 @@ class TestCommandHandler(BaseTest):
 
     def test_deprecation_warning(self):
         """``allow_edited`` deprecated in favor of filters"""
-        with pytest.warns(TelegramDeprecationWarning, match='See https://git.io/fxJuV'):
+        with pytest.warns(
+            TelegramDeprecationWarning,
+            match='See https://github.com/python-telegram-bot/python-telegram-bot/wiki'
+            '/Transition-guide-to-Version-12.0',
+        ):
             self.make_default_handler(allow_edited=True)
 
     def test_edited(self, command_message):

tests/test_messagehandler.py

@@ -149,11 +149,23 @@ class TestMessageHandler:
         assert self.test_flag
 
     def test_deprecation_warning(self):
-        with pytest.warns(TelegramDeprecationWarning, match='See https://git.io/fxJuV'):
+        with pytest.warns(
+            TelegramDeprecationWarning,
+            match='See https://github.com/python-telegram-bot/python-telegram-bot/wiki'
+            '/Transition-guide-to-Version-12.0',
+        ):
             MessageHandler(None, self.callback_basic, edited_updates=True)
-        with pytest.warns(TelegramDeprecationWarning, match='See https://git.io/fxJuV'):
+        with pytest.warns(
+            TelegramDeprecationWarning,
+            match='See https://github.com/python-telegram-bot/python-telegram-bot/wiki'
+            '/Transition-guide-to-Version-12.0',
+        ):
             MessageHandler(None, self.callback_basic, message_updates=False)
-        with pytest.warns(TelegramDeprecationWarning, match='See https://git.io/fxJuV'):
+        with pytest.warns(
+            TelegramDeprecationWarning,
+            match='See https://github.com/python-telegram-bot/python-telegram-bot/wiki'
+            '/Transition-guide-to-Version-12.0',
+        ):
             MessageHandler(None, self.callback_basic, channel_post_updates=True)
 
     def test_edited_deprecated(self, message):