From: George Zaguri via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Timo Rothenpieler <code@ffmpeg.org>,
George Zaguri <george.zaguri@gmail.com>
Subject: [FFmpeg-devel] Re: [PR] forgejo/workflows: explicitly name all workflows and jobs (PR #21357)
Date: Fri, 2 Jan 2026 17:42:33 +0000
Message-ID: <CAGQfSO2ee1qXbwLFa7w=_CXexUuuMRfD_+cnf1+-yTDSsnyqaw@mail.gmail.com> (raw)
In-Reply-To: <176736576136.25.7931791327357239409@4457048688e7>
Hello,
I don't know if this is related, but I see here your name instead of mine:
https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/21148 (latest force-push). Is
it a bug which you mentioned here?
All the best,
Georgii Zagoruiko
On Fri, Jan 2, 2026 at 2:56 PM Timo Rothenpieler via ffmpeg-devel <
ffmpeg-devel@ffmpeg.org> wrote:
> PR #21357 opened by Timo Rothenpieler (BtbN)
> URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/21357
> Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/21357.patch
>
> This primarily works around a bug that leads to mass accumulation of
> commit statuses in the database, cause of a bug in Forgejo.
> Though it also makes the Status-List just a little bit nicer to look at.
>
>
> >From efceef1206e0ddf5b63e6fc410510a93065d98b9 Mon Sep 17 00:00:00 2001
> From: Timo Rothenpieler <timo@rothenpieler.org>
> Date: Fri, 2 Jan 2026 15:54:35 +0100
> Subject: [PATCH] forgejo/workflows: explicitly name all workflows and jobs
>
> ---
> .forgejo/workflows/autolabel.yml | 3 +++
> .forgejo/workflows/lint.yml | 3 +++
> .forgejo/workflows/test.yml | 4 ++++
> 3 files changed, 10 insertions(+)
>
> diff --git a/.forgejo/workflows/autolabel.yml
> b/.forgejo/workflows/autolabel.yml
> index cb4dac67aa..d2408fcb26 100644
> --- a/.forgejo/workflows/autolabel.yml
> +++ b/.forgejo/workflows/autolabel.yml
> @@ -1,3 +1,5 @@
> +name: Autolabel
> +
> on:
> pull_request_target:
> types: [opened, edited, synchronize, closed, assigned, labeled,
> unlabeled]
> @@ -8,6 +10,7 @@ on:
>
> jobs:
> pr_labeler:
> + name: Labeler
> runs-on: utilities
> if: ${{ github.event.sender.login != 'ffmpeg-devel' }}
> steps:
> diff --git a/.forgejo/workflows/lint.yml b/.forgejo/workflows/lint.yml
> index 42e925ad8b..4b3a546ad7 100644
> --- a/.forgejo/workflows/lint.yml
> +++ b/.forgejo/workflows/lint.yml
> @@ -1,3 +1,5 @@
> +name: Lint
> +
> on:
> push:
> branches:
> @@ -6,6 +8,7 @@ on:
>
> jobs:
> lint:
> + name: Pre-Commit
> runs-on: utilities
> steps:
> - name: Checkout
> diff --git a/.forgejo/workflows/test.yml b/.forgejo/workflows/test.yml
> index bce6063521..ecb741e98e 100644
> --- a/.forgejo/workflows/test.yml
> +++ b/.forgejo/workflows/test.yml
> @@ -1,3 +1,5 @@
> +name: Test
> +
> on:
> push:
> branches:
> @@ -6,6 +8,7 @@ on:
>
> jobs:
> run_fate:
> + name: Fate
> strategy:
> fail-fast: false
> matrix:
> @@ -58,6 +61,7 @@ jobs:
> find . -name "*.err" -exec printf '::group::%s\n' {} \; -exec
> cat {} \; -exec printf '::endgroup::\n' \;
> exit ${FATERES:-0}
> run_fate_full:
> + name: Fate (Full)
> strategy:
> fail-fast: false
> matrix:
> --
> 2.49.1
>
> _______________________________________________
> ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
> To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
>
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
next prev parent reply other threads:[~2026-01-02 17:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-02 14:56 [FFmpeg-devel] " Timo Rothenpieler via ffmpeg-devel
2026-01-02 17:42 ` George Zaguri via ffmpeg-devel [this message]
2026-01-02 20:04 ` [FFmpeg-devel] " Timo Rothenpieler via ffmpeg-devel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAGQfSO2ee1qXbwLFa7w=_CXexUuuMRfD_+cnf1+-yTDSsnyqaw@mail.gmail.com' \
--to=ffmpeg-devel@ffmpeg.org \
--cc=code@ffmpeg.org \
--cc=george.zaguri@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git