Document how to close issues from commit message

mikolaj commented

2024-08-20 21:46:05 +02:00

Forgejo supports closing issues by mentioning them in a commit message on a new line after a keyword, such as Fixes. For example, adding the following line:

Fixes https://codeberg.org/Codeberg/Documentation/issues/471

would close issue #471 (this issue). However, this functionality and the list of available keywords for this purpose doesn't appear to be documented anywhere in Codeberg's documentation. It would be helpful if it was.

Forgejo supports closing issues by mentioning them in a commit message on a new line after a keyword, such as `Fixes`. For example, adding the following line: ``` Fixes https://codeberg.org/Codeberg/Documentation/issues/471 ``` would close issue #471 (this issue). However, this functionality and the list of available keywords for this purpose doesn't appear to be documented anywhere in Codeberg's documentation. It would be helpful if it was.

👍 1

Gusted commented

2024-08-20 22:15:59 +02:00

Owner

This is currently documented in the Forgejo documentation. https://forgejo.org/docs/latest/user/linked-references/#actionable-references-in-pull-requests-and-commit-messages, not sure if a more user-friendly in the Codeberg documentation is worth it or if it should point to the forgejo docs for this.

mikolaj commented

2024-08-20 22:38:54 +02:00

Author

It seems that I failed to find it despite trying a few times because I was using the keyword "codeberg" instead of "forgejo" in Web search. Though there's a chance that others will have this problem too, I leave it up to y'all to decide whether this is an actionable issue.

Gusted commented

2024-08-20 23:08:27 +02:00

Owner

CC @fnetX - I don't have a clear preference.

fnetX commented

2024-08-20 23:22:14 +02:00

Owner

I think that every content that users cannot find in the codeberg docs is worth tracking - for consideration on how to deal with it at least.

I think @n0toose might want to figure out whether to mirror/sync the content, or maybe ... have a search that also indexes the Forgejo docs?

I think that every content that users cannot find in the codeberg docs is worth tracking - for consideration on how to deal with it at least. I think @n0toose might want to figure out whether to mirror/sync the content, or maybe ... have a search that also indexes the Forgejo docs?

👍 1

fogti commented

2024-10-17 21:07:51 +02:00

A search that also indexes Forgejo docs would be pretty helpful, as it is currently very non-obvious how to search Forgejo docs, and it is often necessary to search both anyways (the end user per default doesn't really know what is Forgejo and what is downstream modification, etc.)

n0toose added the

Forgejo

label

2025-05-14 17:41:50 +02:00

Rows
Columns

Document how to close issues from commit message #471