As we can store arbitrary data in the git storage and reference it in a commit, we can support media in bug's comment.

In particular, we can have:

• images (jpg, png, gif ..)
• video (as supported by major browser)
• arbitrary files

Markdown support images but not video (though gitlab reuse the same syntax: https://gitlab.com/help/user/markdown#videos), nor arbitrary files.

On top of that, as files would not be in the normal repository, we need a way to reference the corresponding blob.

A way to do that might be:

Inline-style:
![alt text](e69de29bb2d1d6434b8b29ae775ad8c2e48c5391 "logo.png")

Reference-style:
![alt text1][logo]

[logo]: e69de29bb2d1d6434b8b29ae775ad8c2e48c5391 "logo.png"

Additionally, git-bug could enforce the reference style to make it more readable for terminal users.

Michael Muré (MichaelMure) added label RFC 7 years ago

Michael Muré (MichaelMure) added label enhancement 7 years ago

Michael Muré (MichaelMure) added label Core 7 years ago

Would it be possible to use the webui to paste an image? (begging the additional question of using the webui for issue creation/editing)

@nkgm yes, that would be totally neat. I'd love to have the same UX as on github.

This bot triages untriaged issues and PRs according to the following rules:

• After 90 days of inactivity, the lifecycle/stale label is applied
• After 30 days of inactivity since lifecycle/stale was applied, the issue is closed

To remove the stale status, you can:

• Remove the lifecycle/stale label
• Comment on this issue

github-actions (github-actions) added label lifecycle/stale 1 year ago

Seeing as this feature is on the planned feature matrix at https://github.com/MichaelMure/git-bug/blob/master/doc/feature_matrix.md#entities, I don't think it makes sense to make it stale or close it...

github-actions (github-actions) removed label lifecycle/stale 1 year ago

@keith-hall the stale bot was added to aid in pruning issues and pull requests that have not had activity in a while, given the slowdown of development over the past few years. Indeed, this is an issue that is definitely a desirable feature.

sudoforge removed label enhancement 1 year ago

sudoforge removed label RFC 1 year ago

sudoforge removed label Core 1 year ago

sudoforge added label kind/feature 1 year ago

sudoforge added label priority/important-longterm 1 year ago

sudoforge added label triage/accepted 1 year ago

sudoforge added label area/comments 1 year ago

This bot triages issues in order to help the maintainers identify what needs attention, according to the following lifecycle rules:

• After 90 days of inactivity, lifecycle/stale is applied
• After 90 days of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied

This bot will not automatically close stale issues.

To remove the stale status, you can:

• Remove the stale label from this issue
• Comment on this issue
• Close this issue
• Offer to help out with triaging

To avoid automatic lifecycle management of this issue, add lifecycle/frozen.

github-actions (github-actions) added label lifecycle/stale 1 year ago

Not stale

github-actions (github-actions) removed label lifecycle/idle 7 months ago