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

[PR #48] [MERGED] Ordering team by name ascending except for 'Owners' #15112

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

📋 Pull Request Information

Original PR: https://github.com/go-gitea/gitea/pull/48
Author: @thibaultmeyer
Created: 11/3/2016
Status: ✅ Merged
Merged: 11/6/2016
Merged by: @strk

Base: master ← Head: feature/3841-ordering-team-names

📝 Commits (4)

  • 247fe44 Ordering team by name ascending except for 'Owners'
  • f2eb18b Merge branch 'master' into feature/3841-ordering-team-names
  • 3ceb60b Merge branch 'master' into feature/3841-ordering-team-names
  • c595de7 Merge branch 'master' into feature/3841-ordering-team-names

📊 Changes

1 file changed (+4 additions, -4 deletions)

View changed files

📝 models/org.go (+4 -4)

📄 Description

Relative to the issue #3841, this pull request force team names to be ascending ordered. Owners is now always on top of the list.

Tested on MySQL 5, PostgreSQL 9 ans SQlite 3

image

🔄 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/48 **Author:** [@thibaultmeyer](https://github.com/thibaultmeyer) **Created:** 11/3/2016 **Status:** ✅ Merged **Merged:** 11/6/2016 **Merged by:** [@strk](https://github.com/strk) **Base:** `master` ← **Head:** `feature/3841-ordering-team-names` --- ### 📝 Commits (4) - [`247fe44`](https://github.com/go-gitea/gitea/commit/247fe443be92b070826957979805074c1385ee10) Ordering team by name ascending except for 'Owners' - [`f2eb18b`](https://github.com/go-gitea/gitea/commit/f2eb18bf708056807f7373dac40c15964ffb6da9) Merge branch 'master' into feature/3841-ordering-team-names - [`3ceb60b`](https://github.com/go-gitea/gitea/commit/3ceb60b8d0044d96803e09246e56d675291cdde9) Merge branch 'master' into feature/3841-ordering-team-names - [`c595de7`](https://github.com/go-gitea/gitea/commit/c595de77573d4519fa0dad91da976024c42d5d80) Merge branch 'master' into feature/3841-ordering-team-names ### 📊 Changes **1 file changed** (+4 additions, -4 deletions) <details> <summary>View changed files</summary> 📝 `models/org.go` (+4 -4) </details> ### 📄 Description Relative to the issue #3841, this pull request force team names to be ascending ordered. _Owners_ is now always on top of the list. Tested on MySQL 5, PostgreSQL 9 ans SQlite 3 ![image](https://cloud.githubusercontent.com/assets/1005086/19930499/04e6a17c-a109-11e6-891d-f3dc55507b8a.png) --- <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 11:39:07 -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#15112
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?