[PR #6858] [MERGED] docs: github: clarify how to attach logs #6201

New issue

Closed

opened 2026-05-05 10:52:34 -06:00 by gitea-mirror · 0 comments

gitea-mirror commented

2026-05-05 10:52:34 -06:00

Owner

📋 Pull Request Information

Original PR: https://github.com/netblue30/firejail/pull/6858
Author: @kmk3
Created: 8/13/2025
Status: ✅ Merged
Merged: 8/16/2025
Merged by: @kmk3

Base: master ← Head: docs-clarify-log-upload

📝 Commits (1)

1353d7c docs: github: clarify how to attach logs

📊 Changes

1 file changed (+8 additions, -2 deletions)

View changed files

📝 .github/ISSUE_TEMPLATE/bug_report.md (+8 -2)

📄 Description

Link to the GitHub docs for attaching a file[1].

This should be more straightforward in most cases and would avoid
polluting the user profile with gists unnecessarily (which might get in
the way of using/managing other gists), especially over time when
dealing with many projects/issues/comments.

Keep the gist as a fallback option just in case the file attachment
feature randomly gets broken for an extended period of time, as the
GitHub web UI overall keeps getting slower and jankier over time.

Note: It seems that in both cases (attachment/gist), the file size limit
in the web UI is 25MB[2].

Relates to #5398.

Misc: This was noticed on #5611.

[1] https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/attaching-files
[2] https://docs.github.com/en/repositories/working-with-files/managing-large-files/about-large-files-on-github#file-size-limits

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/netblue30/firejail/pull/6858 **Author:** [@kmk3](https://github.com/kmk3) **Created:** 8/13/2025 **Status:** ✅ Merged **Merged:** 8/16/2025 **Merged by:** [@kmk3](https://github.com/kmk3) **Base:** `master` ← **Head:** `docs-clarify-log-upload` --- ### 📝 Commits (1) - [`1353d7c`](https://github.com/netblue30/firejail/commit/1353d7c866e9be82a6371de765cc2708216730fa) docs: github: clarify how to attach logs ### 📊 Changes **1 file changed** (+8 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `.github/ISSUE_TEMPLATE/bug_report.md` (+8 -2) </details> ### 📄 Description Link to the GitHub docs for attaching a file[1]. This should be more straightforward in most cases and would avoid polluting the user profile with gists unnecessarily (which might get in the way of using/managing other gists), especially over time when dealing with many projects/issues/comments. Keep the gist as a fallback option just in case the file attachment feature randomly gets broken for an extended period of time, as the GitHub web UI overall keeps getting slower and jankier over time. Note: It seems that in both cases (attachment/gist), the file size limit in the web UI is 25MB[2]. Relates to #5398. Misc: This was noticed on #5611. [1] https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/attaching-files [2] https://docs.github.com/en/repositories/working-with-files/managing-large-files/about-large-files-on-github#file-size-limits --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

gitea-mirror

2026-05-05 10:52:34 -06:00

closed this issue
added the
pull-request
label

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/firejail#6201

No description provided.

Rows
Columns