Description
I have an error when posting comments using the API on certain repositories.
API PATH:
POST /repos/{owner}/{repo}/issues/{index}/comments
I think I've target the repositories to those who were created in organizations that were created in gitea version 1.6.X, we migrated to 1.7.0 and are unable to post comment using the api
I tested it on a new organization (created on version 1.7.0) and API works fine.
I tested it on a new repository of a user created in 1.6.X and API works fine.
We unfortunately do not have a repository of a user which were both created in version 1.6.x
FYI: we migrated to 1.7.0 from 1.6.4
FYI: we have an auth source of SMTP setup, this happens whether the user is local or SMTP source
Version that were deployed: 1.6.2, 1.6.3, 1.6.4, 1.7.0
curl -X POST \
"https://scm.example.com/api/v1/repos/{org}/{repo}/issues/{index}/comments" \
-H "accept: application/json" \
-H "Authorization: token {censured}d5397f04095dc53887e1d2099cf4" \
-H "Content-Type: application/json" \
-d "{ \"body\": \"This comment was sent using the API\"}"
The above curl responds with a 500 error, logs are available in gist above
Other API calls are working fine, whether their POST's or GET's, didn't test them all tough
[x]):Description
I have an error when posting comments using the API on certain repositories.
API PATH:
POST /repos/{owner}/{repo}/issues/{index}/commentsI think I've target the repositories to those who were created in organizations that were created in gitea version 1.6.X, we migrated to 1.7.0 and are unable to post comment using the api
I tested it on a new organization (created on version 1.7.0) and API works fine.
I tested it on a new repository of a user created in 1.6.X and API works fine.
We unfortunately do not have a repository of a user which were both created in version 1.6.x
FYI: we migrated to 1.7.0 from 1.6.4
FYI: we have an auth source of SMTP setup, this happens whether the user is local or SMTP source
Version that were deployed: 1.6.2, 1.6.3, 1.6.4, 1.7.0
The above curl responds with a 500 error, logs are available in gist above
Other API calls are working fine, whether their POST's or GET's, didn't test them all tough