Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Yalda <code@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Subject: [FFmpeg-devel] [PATCH] forgejo/ISSUE_TEMPLATE: create Issue ticket template based on TRAC form (PR #20107)
Date: Mon,  4 Aug 2025 06:03:04 +0300 (EEST)
Message-ID: <20250804030304.A334568C1A0@ffbox0-bg.ffmpeg.org> (raw)

PR #20107 opened by Yalda
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20107
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20107.patch

This is based on the previously used, simple TRAC form
with new description language.

We can iterate on it to improve as needed.

Note I put this in my master branch so folks can go to my branch and see it.


>From ec1fc4306e88479c1fde7f7fd4e87277a9f06dbb Mon Sep 17 00:00:00 2001
From: Yalda <marth64@proxyid.net>
Date: Mon, 4 Aug 2025 03:01:16 +0000
Subject: [PATCH] forgejo/ISSUE_TEMPLATE: create Issue ticket template based on
 TRAC form

This is based on the previously used, simple TRAC form
with new description language.

We can iterate on it to improve as needed.

Signed-off-by: Yalda <marth64@proxyid.net>
---
 .forgejo/ISSUE_TEMPLATE.md | 9 +++++++++
 1 file changed, 9 insertions(+)
 create mode 100644 .forgejo/ISSUE_TEMPLATE.md

diff --git a/.forgejo/ISSUE_TEMPLATE.md b/.forgejo/ISSUE_TEMPLATE.md
new file mode 100644
index 0000000000..d58e832b73
--- /dev/null
+++ b/.forgejo/ISSUE_TEMPLATE.md
@@ -0,0 +1,9 @@
+# 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.
-- 
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-04  3:03 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=20250804030304.A334568C1A0@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