Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "Kacper Michajłow" <code@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Subject: [FFmpeg-devel] [PATCH] forgejo/ISSUE_TEMPLATE: ask for more information in issue template (PR #20123)
Date: Tue,  5 Aug 2025 20:25:21 +0300 (EEST)
Message-ID: <20250805172521.061B868C6C8@ffbox0-bg.ffmpeg.org> (raw)

PR #20123 opened by Kacper Michajłow (kasper93)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20123
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20123.patch

Signed-off-by: Kacper Michajłow <kasper93@gmail.com>


From 8930558b83f69ced7b22813bf9271a06955e7dd5 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Kacper=20Michaj=C5=82ow?= <kasper93@gmail.com>
Date: Tue, 5 Aug 2025 19:06:39 +0200
Subject: [PATCH] forgejo/ISSUE_TEMPLATE: ask for more information in issue
 template
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Signed-off-by: Kacper Michajłow <kasper93@gmail.com>
---
 .forgejo/ISSUE_TEMPLATE.md   |  9 ----
 .forgejo/ISSUE_TEMPLATE.yaml | 91 ++++++++++++++++++++++++++++++++++++
 2 files changed, 91 insertions(+), 9 deletions(-)
 delete mode 100644 .forgejo/ISSUE_TEMPLATE.md
 create mode 100644 .forgejo/ISSUE_TEMPLATE.yaml

diff --git a/.forgejo/ISSUE_TEMPLATE.md b/.forgejo/ISSUE_TEMPLATE.md
deleted file mode 100644
index d58e832b73..0000000000
--- a/.forgejo/ISSUE_TEMPLATE.md
+++ /dev/null
@@ -1,9 +0,0 @@
-# Summary of the bug
-
-Briefly describe the issue you're experiencing. Include any error messages, unexpected behavior, or relevant observations.
-
-# Steps to reproduce
-
-List the steps required to trigger the bug.
-Include the exact CLI command used, if any.
-Provide sample input files, logs, or scripts if available.
diff --git a/.forgejo/ISSUE_TEMPLATE.yaml b/.forgejo/ISSUE_TEMPLATE.yaml
new file mode 100644
index 0000000000..f1f12f61aa
--- /dev/null
+++ b/.forgejo/ISSUE_TEMPLATE.yaml
@@ -0,0 +1,91 @@
+name: "Report an Issue"
+description: "Create a report for a runtime related Issue"
+labels: []
+type: Bug
+body:
+- type: textarea
+  attributes:
+      label: "FFmpeg Information"
+      placeholder: |
+          ffmpeg version n7.1.1 Copyright (c) 2000-2025 the FFmpeg developers
+          built with gcc 14 (Debian 14.2.0-19)
+          configuration:
+          libavutil      59. 39.100 / 59. 39.100
+          libavcodec     61. 19.101 / 61. 19.101
+          libavformat    61.  7.100 / 61.  7.100
+          libavdevice    61.  3.100 / 61.  3.100
+          libavfilter    10.  4.100 / 10.  4.100
+          libswscale      8.  3.100 /  8.  3.100
+          libswresample   5.  3.100 /  5.  3.100
+      description: |
+          Provide the output of `ffmpeg -version`, if applicable.
+      render: bash
+  validations:
+      required: false
+- type: textarea
+  attributes:
+      label: "Important Information"
+      description: >
+          - Platform and Version
+           - CPU Architecture
+           - GPU model, driver and version
+           - Source of the ffmpeg binaries
+           - Latest version of ffmpeg you know without the problem
+
+
+          If you're not using git master or the latest release, try it first, if possible.
+
+
+          Additional relevant information is appreciated, especially for hardware/platform specific issues.
+      value: |-
+          - Platform version:
+          - CPU Architecture:
+          - GPU model, driver and version:
+          - Source of the ffmpeg binaries:
+          - Latest known working version:
+          - Issue started after the following happened:
+      render: text
+  validations:
+      required: true
+- type: textarea
+  attributes:
+      label: "Reproduction Steps"
+      description: >
+          List the steps required to trigger the bug.
+
+
+          Include the exact CLI command used, if any.
+  validations:
+      required: true
+- type: textarea
+  attributes:
+      label: "Expected Behavior"
+      placeholder: "What were you expecting?"
+  validations:
+      required: true
+- type: textarea
+  attributes:
+      label: "Actual Behavior"
+      placeholder: "What happened instead?"
+  validations:
+      required: true
+- type: textarea
+  attributes:
+      label: "Log File"
+      placeholder: "Drag and drop log file here (Don't paste content directly)"
+      description: >
+          Include the exact CLI command used, if any and its output.
+  validations:
+      required: true
+- type: textarea
+  attributes:
+      label: "Sample Files or other additional files"
+      placeholder: "Drag and drop sample files here"
+      description: >
+          Please provide sample files for a minimal reproduction case, if the issue can't be
+          reproduced without it or it is helpful to demonstrate the issue.
+
+
+          Preferably files should be attached directly within the text field below. If the sample
+          file is too big to attach directly, use a solution that is easy to access with possible
+          long-term retention.
-- 
2.49.1

_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

                 reply	other threads:[~2025-08-05 17:25 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20250805172521.061B868C6C8@ffbox0-bg.ffmpeg.org \
    --to=code@ffmpeg.org \
    --cc=ffmpeg-devel@ffmpeg.org \
    /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