Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RocketChat notification for pull request comment has not working hyperlink #7973

Closed
2 of 7 tasks
mathysie opened this issue Aug 25, 2019 · 5 comments
Closed
2 of 7 tasks
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented type/bug
Milestone

Comments

@mathysie
Copy link

mathysie commented Aug 25, 2019

  • Gitea version (or commit ref): 1.9.2
  • Git version:
  • Operating system: Ubuntu 18.04
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:

Description

After placing a comment in a pull request, a notification is send to our Rocket.Chat. The notification tries to provide a hyperlink to the message with the syntax <"hyperlink"|"name pull request">. This is correct, however it is used as a header as well. Therefore, instead of making a hyperlink to the Gitea server, Rocket.Chat creates a hyperlink to show the contents of the comment.

I suggest to change the comment notification to:

[foo] New comment created by <"hyperlink to user"|"user">: <"hyperlink to comment"|"name pull request">
> "Comment contents"

This method will render all hyperlinks correctly.

Screenshots

Schermafdruk van 2019-08-25 14-11-30

@mathysie mathysie changed the title RocketChat notification has not working hyperlink to pull request comment RocketChat notification for pull request comment has not working hyperlink Aug 25, 2019
@lunny
Copy link
Member

lunny commented Aug 25, 2019

Which webhook type did you use?

@mathysie
Copy link
Author

We are using the slack hook

@stale
Copy link

stale bot commented Oct 24, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale stale bot added the issue/stale label Oct 24, 2019
@lunny lunny added the issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented label Nov 2, 2019
@stale stale bot removed the issue/stale label Nov 2, 2019
@lunny lunny added the type/bug label Nov 2, 2019
@cornelk
Copy link
Contributor

cornelk commented Jan 5, 2020

@mathysie please test again with v1.10.2 or later, this should be fixed with #9422

@lafriks lafriks added this to the 1.11.0 milestone Jan 5, 2020
@lafriks
Copy link
Member

lafriks commented Jan 5, 2020

Closing as fixed, reopen if there is still a problem

@lafriks lafriks closed this as completed Jan 5, 2020
@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented type/bug
Projects
None yet
Development

No branches or pull requests

4 participants