From cd501d5fe03d9116db8b69265da51afb26386b42 Mon Sep 17 00:00:00 2001 From: Hinrich Mahler <22366557+Bibo-Joshi@users.noreply.github.com> Date: Fri, 1 Nov 2024 18:12:25 +0100 Subject: [PATCH 1/2] Fix Linkcheck Workflow --- .github/workflows/docs-linkcheck.yml | 5 ++++- README.rst | 4 ++-- telegram/_files/inputfile.py | 4 ++-- 3 files changed, 8 insertions(+), 5 deletions(-) diff --git a/.github/workflows/docs-linkcheck.yml b/.github/workflows/docs-linkcheck.yml index f34fcc17d22..7a9b9a498c8 100644 --- a/.github/workflows/docs-linkcheck.yml +++ b/.github/workflows/docs-linkcheck.yml @@ -3,6 +3,9 @@ on: schedule: # First day of month at 05:46 in every 2nd month - cron: '46 5 1 */2 *' + pr: + paths: + - .github/workflows/docs-linkcheck.yml jobs: test-sphinx-build: @@ -10,7 +13,7 @@ jobs: runs-on: ${{matrix.os}} strategy: matrix: - python-version: [3.10] + python-version: ['3.10'] os: [ubuntu-latest] fail-fast: False steps: diff --git a/README.rst b/README.rst index 035180a3ce0..aba1c2c09fd 100644 --- a/README.rst +++ b/README.rst @@ -121,7 +121,7 @@ To enable you to verify that a release file that you downloaded was indeed provi Starting with v21.4, all releases are signed via `sigstore `_. The corresponding signature files are uploaded to the `GitHub releases page`_. -To verify the signature, please install the `sigstore Python client `_ and follow the instructions for `verifying signatures from GitHub Actions `_. As input for the ``--repository`` parameter, please use the value ``python-telegram-bot/python-telegram-bot``. +To verify the signature, please install the `sigstore Python client `_ and follow the instructions for `verifying signatures from GitHub Actions `_. As input for the ``--repository`` parameter, please use the value ``python-telegram-bot/python-telegram-bot``. Earlier releases are signed with a GPG key. The signatures are uploaded to both the `GitHub releases page`_ and the `PyPI project `_ and end with a suffix ``.asc``. @@ -232,4 +232,4 @@ License You may copy, distribute and modify the software provided that modifications are described and licensed for free under `LGPL-3 `_. 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. -.. _`GitHub releases page`: https://github.com/python-telegram-bot/python-telegram-bot/releases> +.. _`GitHub releases page`: https://github.com/python-telegram-bot/python-telegram-bot/releases diff --git a/telegram/_files/inputfile.py b/telegram/_files/inputfile.py index d376d16a106..61e5a94192d 100644 --- a/telegram/_files/inputfile.py +++ b/telegram/_files/inputfile.py @@ -56,8 +56,8 @@ class InputFile: read_file_handle (:obj:`bool`, optional): If :obj:`True` and :paramref:`obj` is a file handle, the data will be read from the file handle on initialization of this object. If :obj:`False`, the file handle will be passed on to the - `networking backend `_ which will have to - handle the reading. Defaults to :obj:`True`. + :attr:`networking backend ` which will have + to handle the reading. Defaults to :obj:`True`. Tip: If you upload extremely large files, you may want to set this to :obj:`False` to From 3dfda33ccbd567dc766014d99b89cd3c36dbb7ca Mon Sep 17 00:00:00 2001 From: Hinrich Mahler <22366557+Bibo-Joshi@users.noreply.github.com> Date: Fri, 1 Nov 2024 20:56:55 +0100 Subject: [PATCH 2/2] fix workflow syntax --- .github/workflows/docs-linkcheck.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/docs-linkcheck.yml b/.github/workflows/docs-linkcheck.yml index 7a9b9a498c8..ea78626c31b 100644 --- a/.github/workflows/docs-linkcheck.yml +++ b/.github/workflows/docs-linkcheck.yml @@ -3,7 +3,7 @@ on: schedule: # First day of month at 05:46 in every 2nd month - cron: '46 5 1 */2 *' - pr: + pull_request: paths: - .github/workflows/docs-linkcheck.yml pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy