feat: api endpoints for projects

[dineshsalunke]

Fixes #14299

My earlier PR #20208 went too long and became messy, so I am closing that one and will be splitting the work in smaller chunks.

This PR includes all the endpoints for the Projects

• POST /user/projects
• POST /orgs/{org}/projects
• POST /repos/{owner}/{repo}/projects
• GET /user/projects
• GET /orgs/{org}/projects
• GET /repos/{owner}/{repo}/projects
• GET /projects/{id}
• PATCH /projects/{id}
• DELETE /projects/{id}

For all the endpoints related to Boards I will be raising another PR for the same.

[denyskon]

@dineshsalunke Is the PR still WIP or is it ready for review?

[dineshsalunke]

@denyskon this one is ready for review

[GamerGirlandCo]

looks good to me!

[denyskon]

@dineshsalunke I see a lot of unrelated formatting changes, maybe originating from your editor formatter or similar. Could you revert them?

[dineshsalunke]

@denyskon I have fixed the golines formatting and pushed.
as for the indentation I am not sure where it is coming from, since my editor is showing it correctly.

I will still check on it and get back

[denyskon]

@dineshsalunke Thank you, however unfortunately some are still remaining in routers/api/v1/api.go.....

[denyskon]

Also, some methods seem to have broken when updating to main. Could you take a look please?

[dineshsalunke]

@denyskon I have pushed some changes for now, which only include the POST methods the test's are passing for them.

Work on PR was slow due to the fact that I didn't had a clear way to handle permissions for /org and /repos routes.

I will look into the permissions thing now for all the POST methods and will push those changes first if the approach looks good to others then I will move with implementing rest of the routes

[lunny]

@dineshsalunke I’ve pushed some changes. When you have a moment, please review them.

[dineshsalunke]

@lunny thanks for the push, i checked and everything looks good.
Also on side note I noticed that there are no fixtures for project on organization, is this expected or I am missing something.

For now, i am adding few fixtures for projects on org as i need them for testing org related project api endpoints

[lunny]

I’ve pushed some commits to update the Swagger documentation. However, it’s still missing permission and resource checks, particularly for the /projects/{project_id} routes.

[MoreQuestions]

Voicing support for this. Without a Projects API, the entire Projects functionality is unusable for any workflow involving automation. It's a great feature that I simply can't use at all in my system with lacking API support.

Imagine being able to automatically create project cards from CI/CD pipelines, move issues across columns based on PR status, or sync project boards with external tools. Gitea could become a true all-in-one DevOps hub. Really looking forward to seeing this land! 👀