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

[PR #4089] [MERGED] add simple descriptions for file API responses #17236

New Issue
Closed
opened 2025-11-02 12:30:28 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-02 12:30:28 -06:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/go-gitea/gitea/pull/4089
Author: @stevegt
Created: 5/30/2018
Status: ✅ Merged
Merged: 6/1/2018
Merged by: @lunny

Base: master ← Head: fix-api-200s

📝 Commits (3)

  • 3a28581 add simple descriptions for file API responses
  • 16dbfa3 Merge branch 'master' into fix-api-200s
  • 3a0e0ab Merge branch 'master' into fix-api-200s

📊 Changes

2 files changed (+15 additions, -6 deletions)

View changed files

📝 public/swagger.v1.json (+9 -3)
📝 routers/api/v1/repo/file.go (+6 -3)

📄 Description

Swagger needs a description field in each swagger:operation response. Adding
minimal text for now on the way to getting swagger validate to pass. Many
standard swagger client libraries will not work with gitea until validate
passes, so prioritizing that over better descriptions for now.

Signed-off-by: Steve Traugott stevegt@t7a.org

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/go-gitea/gitea/pull/4089 **Author:** [@stevegt](https://github.com/stevegt) **Created:** 5/30/2018 **Status:** ✅ Merged **Merged:** 6/1/2018 **Merged by:** [@lunny](https://github.com/lunny) **Base:** `master` ← **Head:** `fix-api-200s` --- ### 📝 Commits (3) - [`3a28581`](https://github.com/go-gitea/gitea/commit/3a285816f9425d0c1f564c14c48af31c4baa55a5) add simple descriptions for file API responses - [`16dbfa3`](https://github.com/go-gitea/gitea/commit/16dbfa350679f9ac2bf7d86021020ca614df6cd8) Merge branch 'master' into fix-api-200s - [`3a0e0ab`](https://github.com/go-gitea/gitea/commit/3a0e0abfe6ce4afddcaada266d77ae733f111b73) Merge branch 'master' into fix-api-200s ### 📊 Changes **2 files changed** (+15 additions, -6 deletions) <details> <summary>View changed files</summary> 📝 `public/swagger.v1.json` (+9 -3) 📝 `routers/api/v1/repo/file.go` (+6 -3) </details> ### 📄 Description * Partial fix for #4010 Swagger needs a description field in each swagger:operation response. Adding minimal text for now on the way to getting swagger validate to pass. Many standard swagger client libraries will not work with gitea until validate passes, so prioritizing that over better descriptions for now. Signed-off-by: Steve Traugott <stevegt@t7a.org> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2025-11-02 12:30:28 -06:00
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 pull-request
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#17236
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?