github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-16 05:02:29 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

GET vs POST swagger.json #1525

New Issue
Closed
opened 2025-11-02 04:03:52 -06:00 by GiteaMirror · 4 comments
GiteaMirror commented 2025-11-02 04:03:52 -06:00
Owner
Copy Link

Originally created by @flyinprogrammer on GitHub (Feb 13, 2018).

Was this file generated?
fbdc00f464/public/swagger.v1.json (L3227)

It seems this is using that json file:
https://try.gitea.io/api/swagger#/

But then what's going on between these three methods?
https://github.com/go-gitea/gitea/blob/master/routers/api/v1/repo/release.go#L16
https://github.com/go-gitea/gitea/blob/master/routers/api/v1/repo/release.go#L59
https://github.com/go-gitea/gitea/blob/master/routers/api/v1/repo/release.go#L99

And why is the swagger json wrong?
I'm happy to submit a patch - I just wasn't quite sure what was going on!

Originally created by @flyinprogrammer on GitHub (Feb 13, 2018). Was this file generated? https://github.com/go-gitea/gitea/blob/fbdc00f46461bec024026b23f85fd1933ead6a96/public/swagger.v1.json#L3227 It seems this is using that json file: https://try.gitea.io/api/swagger#/ But then what's going on between these three methods? https://github.com/go-gitea/gitea/blob/master/routers/api/v1/repo/release.go#L16 https://github.com/go-gitea/gitea/blob/master/routers/api/v1/repo/release.go#L59 https://github.com/go-gitea/gitea/blob/master/routers/api/v1/repo/release.go#L99 And why is the swagger json wrong? I'm happy to submit a patch - I just wasn't quite sure what was going on!
GiteaMirror added the type/bug label 2025-11-02 04:03:52 -06:00
GiteaMirror commented 2025-11-02 04:03:53 -06:00
Author
Owner
Copy Link

@captn3m0 commented on GitHub (Apr 17, 2018):

👍

image

However, this seems to be fixed on try.gitea.io somehow?

image

I'm running 1.4.0+3-g641d481 which shouldn't be far from master.

@captn3m0 commented on GitHub (Apr 17, 2018): :+1: ![image](https://user-images.githubusercontent.com/584253/38891647-99a50e34-42a2-11e8-8ae9-769233b30ab9.png) However, this seems to be fixed on `try.gitea.io` somehow? ![image](https://user-images.githubusercontent.com/584253/38891700-b91345ce-42a2-11e8-8a8e-5d3b1e8b9db8.png) I'm running `1.4.0+3-g641d481` which shouldn't be far from master.
GiteaMirror commented 2025-11-02 04:03:53 -06:00
Author
Owner
Copy Link

@sapk commented on GitHub (Apr 17, 2018):

It was added/fixed by #3478 but it hadn't be backported to v1.4 branch since it is a new feature. I submitted #3811 to be sure that swagger is generated in PR that need it.

@sapk commented on GitHub (Apr 17, 2018): It was added/fixed by #3478 but it hadn't be backported to v1.4 branch since it is a new feature. I submitted #3811 to be sure that swagger is generated in PR that need it.
GiteaMirror commented 2025-11-02 04:03:53 -06:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Jan 28, 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 28, 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:03:53 -06:00
Author
Owner
Copy Link

@adelowo commented on GitHub (Jan 28, 2019):

I believe this can be closed

@adelowo commented on GitHub (Jan 28, 2019): I believe this can be closed
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label type/bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#1525
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?