FR: Create pull request comment via API #2395

New Issue

GiteaMirror · 2025-11-02T04:34:43-06:00

GiteaMirror commented

2025-11-02 04:34:43 -06:00

Originally created by @marvincaspar on GitHub (Oct 10, 2018).

Description

In our CI/CD pipeline we use a static code analysis and I want to create a job, which creates comments on a pull request file if there is a code smell.

I didn't find any API call for this action.

Originally created by @marvincaspar on GitHub (Oct 10, 2018). ## Description In our CI/CD pipeline we use a static code analysis and I want to create a job, which creates comments on a pull request file if there is a code smell. I didn't find any API call for this action.

GiteaMirror added the issue/confirmed type/feature modifies/api labels 2025-11-02 04:34:43 -06:00

GiteaMirror closed this issue

2025-11-02 04:34:43 -06:00

GiteaMirror commented

2025-11-02 04:34:44 -06:00

@jmls commented on GitHub (Oct 15, 2018):

On a more general note - surely it would be better practice to "eat your own dog food" and make the gitea UI only use publicly available api calls ? That way any shortcomings in the api would be exposed very quickly.

There are several instances where the api does not have the same functionality as the UI - yet the UI has to be calling some rest endpoint

@jmls commented on GitHub (Oct 15, 2018): On a more general note - surely it would be better practice to "eat your own dog food" and make the gitea UI only use publicly available api calls ? That way any shortcomings in the api would be exposed very quickly. There are several instances where the api does not have the same functionality as the UI - yet the UI *has* to be calling some rest endpoint

GiteaMirror commented

2025-11-02 04:34:44 -06:00

@stale[bot] commented on GitHub (Jan 6, 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[bot] commented on GitHub (Jan 6, 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.

GiteaMirror commented

2025-11-02 04:34:44 -06:00

@andrzejressel commented on GitHub (Jan 12, 2019):

@mc388 You can use issue comment api for that: https://try.gitea.io/api/swagger#/issue/issueCreateComment

I've just checked that and it works fine.

@andrzejressel commented on GitHub (Jan 12, 2019): @mc388 You can use issue comment api for that: https://try.gitea.io/api/swagger#/issue/issueCreateComment I've just checked that and it works fine.

GiteaMirror commented

2025-11-02 04:34:44 -06:00

@lunny commented on GitHub (Jan 16, 2019):

@jereksel I think he means comment on code lines on pull request review.

@lunny commented on GitHub (Jan 16, 2019): @jereksel I think he means comment on code lines on pull request review.

GiteaMirror commented

2025-11-02 04:34:45 -06:00

@marvincaspar commented on GitHub (Jan 16, 2019):

Thats right @lunny

@marvincaspar commented on GitHub (Jan 16, 2019): Thats right @lunny

GiteaMirror commented

2025-11-02 04:34:45 -06:00

@stale[bot] commented on GitHub (Mar 17, 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[bot] commented on GitHub (Mar 17, 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.

GiteaMirror commented

2025-11-02 04:34:45 -06:00

@6543 commented on GitHub (Nov 5, 2019):

@marvincaspar can we close this in faifour of https://github.com/go-gitea/gitea/issues/5733

@6543 commented on GitHub (Nov 5, 2019): @marvincaspar can we close this in faifour of https://github.com/go-gitea/gitea/issues/5733

GiteaMirror referenced this issue

2025-11-02 12:09:26 -06:00

[PR #2395] [MERGED] fix wrong changelog title #16387

Sign in to join this conversation.