@lichuanqi Can we close this?

You are using sonarqube community. Have you installed the required plugin? https://codeberg.org/justusbunsi/gitea-sonarqube-bot#requirements

Hi there. The bot receives a webhook from SonarQube and uses only those information to post the status code. That's why that part is working.

`Error composing Gitea comment: Insufficient...

@kamp Did you get it working?

Possible autodiscovery approach

Technical requirements

Depend on [sonar.links.scm scanner property](https://docs.sonarsource.com/sonarqube-server/latest/analyzing-source-code/analysis-...

Possible autodiscovery approach

Technical requirements

Depend on [sonar.links.scm scanner property](https://docs.sonarsource.com/sonarqube-server/latest/analyzing-source-code/analysis-...

🙂 Just saw that you edited your message. Glad you got the PR scan working.

The bot can handle every Gitea Pull Request, no matter how it is titled or how the branch is called. Users don't need to follow a naming convention here. Don't worry.

Every Pull Request has its...

Ah, I got it and your guess is totally correct. Seems like the workflow graphic in the README is not clear about it: The bot is more or less a Middleware between Gitea and SonarQube to simulate...

The "PR-11" is default behavior, based on Jenkins plugin build behavior. You probably have to adjust the "namingPattern" settings https://codeberg.org/justusbunsi/gitea-sonarqube-bot/src/commit/99f...

Hrm. The token should be fine. Let's investigate the webhook a bit more: In the webhook config page in Gitea, there are recent webhook deliveries. What's the "X-Gitea-Event" header content? Should...

Hi. Thanks for reaching out and sorry for not responding earlier. Depending on Gitea version (speaking of token scopes), the Gitea account token requires code and issue/pulls permissions. I still...