gogs / gogs/gogs

REST API Endpoints Release

Open
#8,187 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

🎯 feature
Dominant language
Go
Stars
47.8k
Forks
5.1k
Avg merge
7h 23m
Merged PRs (30d)
5

Description

Describe the feature

Please add create / update / delete api endpoints for releases per repository.

Describe the solution you'd like

Example:

CREATE - POST api/v1/repos/{owner}/{repo}/releases/new

Payload:

{
     tag_name: <string>
     tag_target: <string>
      title: <string>
      content: <string>
      files: [<binary>, ...]
}

UPDATE - PUT api/v1/repos/{owner}/{repo}/releases/

Payload:

{
     tag_target: <string>
      title: <string>
      content: <string>
      files: [<binary>, ...]
}

REMOVE - DELETE api/v1/repos/{owner}/{repo}/releases/

Describe alternatives you've considered

The alternative is to provide an ci/cd template like gitlab ci file.

Additional context

No response

Code of Conduct
  • I agree to follow this project's Code of Conduct

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named. Start by locating the existing REST API handlers and release or tag model code, then compare their conventions with the requested repository-scoped routes. Done means create, update, and delete release endpoints support the specified fields and repository paths, including attached files.

Written by the indexing model from the issue text.

Assessment

Tech stack
git, go
Domain
api, release
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.