Add 1 more answers to user stories

Signed-off-by: Akashdeep Dhar <akashdeep.dhar@gmail.com>

docs/dist-git-comparison/forgejo.rst

@@ -191,7 +191,7 @@ Following is the investigation on Forgejo based on the user stories collected.
       While I suggest rebasing and applying changes based on the review comments for a cleaner Git history, it is technically impossible (https://forgejo.org/docs/latest/user/pull-requests-and-git-flow/) for collaborators to apply the suggest changes with a click of a button on GitLab.
 
 57. **As a package maintainer, I would like to be able to automatically transfer issues between packages (for example from ansible -> ansible-core).**
-      This is unfortunately impossible in Forgejo and in order to pull off something like this, one would have to make use of their REST API (https://forgejo.org/docs/latest/user/api-usage/) to delete the issue ticket from the source namespace and create a new instance of it at the destination namespace.
+      This is unfortunately impossible in Forgejo and in order to pull off something like this, one would have to make use of their REST API (https://forgejo.org/docs/latest/user/api-usage/) to close or delete the issue ticket from the source namespace and create a new instance of it at the destination namespace, and point to the issue ticket at the source namespace if closed in the comments.
 
 58. **A package maintainer, I would like a push hook to block pushes to retired or EOL branches**
       While a relevant documentation could not be found on the matter, as Forgejo is based on Git version control system - it should be theoretically possible to conditionalize the rejection of a pushed commit whenever they are made against a branch that is slated to be retired or EOLed. The absence of a documentation means that more efforts has to be put into it.
@@ -258,3 +258,6 @@ Following is the investigation on Forgejo based on the user stories collected.
 
 79. **As a package maintainer, I want to have syntax highlighting for RPM spec files in the git forge web interface. Currently Pagure and Forgejo have this, but GitLab does not.**
       Good point! We can ask the GitLab folks nicely to add that I suppose.
+
+80. **As a Fedora Badges junkie, I want to be able to receive badges for activities related to dist-git. In technical terms, the dist-git activities must be broadcast to the Fedora Message Bus (or however it's called nowadays).**
+      Please check the answer to the user story #51.

docs/dist-git-comparison/gitlab.rst

@@ -266,3 +266,6 @@ Following is the investigation on GitLab based on the user stories collected.
 
 79. **As a package maintainer, I want to have syntax highlighting for RPM spec files in the git forge web interface. Currently Pagure and Forgejo have this, but GitLab does not.**
       Good point! We can ask the GitLab folks nicely to add that I suppose.
+
+80. **As a Fedora Badges junkie, I want to be able to receive badges for activities related to dist-git. In technical terms, the dist-git activities must be broadcast to the Fedora Message Bus (or however it's called nowadays).**
+      Please check the answer to the user story #51.

docs/dist-git-comparison/stories.rst

@@ -244,3 +244,6 @@ Following is the investigation on GitLab based on the user stories collected.
 
 79. **As a package maintainer, I want to have syntax highlighting for RPM spec files in the git forge web interface. Currently Pagure and Forgejo have this, but GitLab does not.**
       `Reported <https://pagure.io/fedora-infra/arc/issue/164#comment-930375>`_ by **Carl W. George** (``carlwgeorge``)
+
+80. **As a Fedora Badges junkie, I want to be able to receive badges for activities related to dist-git. In technical terms, the dist-git activities must be broadcast to the Fedora Message Bus (or however it's called nowadays).**
+      `Reported <https://pagure.io/fedora-infra/arc/issue/164#comment-931576>`_ by **Miro Hroncok** (``churchyard``)