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

[PR #3964] [MERGED] api: repos/search: add parameters to control the sort order #17169

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

📋 Pull Request Information

Original PR: https://github.com/go-gitea/gitea/pull/3964
Author: @aswild
Created: 5/14/2018
Status: ✅ Merged
Merged: 8/2/2018
Merged by: @lunny

Base: master ← Head: repo-search-sort

📝 Commits (6)

  • bc20878 api: repos/search: add parameters to control the sort order
  • 4922691 Merge branch 'master' into repo-search-sort
  • 07f463f Merge branch 'master' into repo-search-sort
  • 5d21d47 Merge branch 'master' into repo-search-sort
  • b959a21 Merge branch 'master' of git://github.com/go-gitea/gitea into repo-search-sort
  • 49d97de Merge branch 'master' of git://github.com/go-gitea/gitea into repo-search-sort

📊 Changes

2 files changed (+59 additions, -0 deletions)

View changed files

📝 routers/api/v1/repo/repo.go (+47 -0)
📝 templates/swagger/v1_json.tmpl (+12 -0)

📄 Description

The backend SearchRepositoryByName function supports several sort order
options, hook these up to the /repos/search API.

New parameters for /repos/search:
'sort': alpha, created, updated, size, or id
'order': 0 for ascending or 1 for descending

'order' defaults to ascending, and is only used when 'sort' is also specified.
The overall default behavior is unchanged (alphabetically ascending).

This partially implements issue #3963

Signed-off-by: Allen Wild allenwild93@gmail.com

🔄 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/3964 **Author:** [@aswild](https://github.com/aswild) **Created:** 5/14/2018 **Status:** ✅ Merged **Merged:** 8/2/2018 **Merged by:** [@lunny](https://github.com/lunny) **Base:** `master` ← **Head:** `repo-search-sort` --- ### 📝 Commits (6) - [`bc20878`](https://github.com/go-gitea/gitea/commit/bc208783ccf3e167902e3d505d4927dcc121c158) api: repos/search: add parameters to control the sort order - [`4922691`](https://github.com/go-gitea/gitea/commit/492269142867c63df19a4988c36048431af03772) Merge branch 'master' into repo-search-sort - [`07f463f`](https://github.com/go-gitea/gitea/commit/07f463f5c0fb106520248207909ad86b6f1cecd5) Merge branch 'master' into repo-search-sort - [`5d21d47`](https://github.com/go-gitea/gitea/commit/5d21d4797373ca92c2a851dc2b3300a0b634ec7a) Merge branch 'master' into repo-search-sort - [`b959a21`](https://github.com/go-gitea/gitea/commit/b959a218752b5066634339d480a4e954d93df572) Merge branch 'master' of git://github.com/go-gitea/gitea into repo-search-sort - [`49d97de`](https://github.com/go-gitea/gitea/commit/49d97de4dc2ed862767efb0d6f6ec7cf64db913a) Merge branch 'master' of git://github.com/go-gitea/gitea into repo-search-sort ### 📊 Changes **2 files changed** (+59 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `routers/api/v1/repo/repo.go` (+47 -0) 📝 `templates/swagger/v1_json.tmpl` (+12 -0) </details> ### 📄 Description The backend SearchRepositoryByName function supports several sort order options, hook these up to the /repos/search API. New parameters for /repos/search: 'sort': alpha, created, updated, size, or id 'order': 0 for ascending or 1 for descending 'order' defaults to ascending, and is only used when 'sort' is also specified. The overall default behavior is unchanged (alphabetically ascending). This partially implements issue #3963 Signed-off-by: Allen Wild <allenwild93@gmail.com> --- <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:28:11 -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#17169
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?