github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-05-08 08:59:13 -05:00
Code Issues 14.5k Packages Projects Releases 120 Wiki Activity

[PR #9270] [MERGED] server: group routes by category and purpose #12905

New Issue
Closed
opened 2026-04-13 00:12:28 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-13 00:12:28 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/ollama/ollama/pull/9270
Author: @bmizerany
Created: 2/21/2025
Status: ✅ Merged
Merged: 2/22/2025
Merged by: @bmizerany

Base: main ← Head: bmizerany/regrouproutes

📝 Commits (3)

  • 2aa076b server: group routes by category and purpose
  • 4015179 Update routes.go
  • 3cfeaad cleanup GET/HEAD loop and just say GET or HEAD.

📊 Changes

3 files changed (+50 additions, -32 deletions)

View changed files

📝 envconfig/config.go (+3 -3)
📝 envconfig/config_test.go (+1 -1)
📝 server/routes.go (+46 -28)

📄 Description

The route assembly in Handler lacked clear organization making it difficult scan for routes and their relationships to each other. This commit aims to fix that by reordering the assembly of routes to group them by category and purpose.

Also, be more specific about what "config" refers to (it is about CORS if you were wondering... I was.)

🔄 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/ollama/ollama/pull/9270 **Author:** [@bmizerany](https://github.com/bmizerany) **Created:** 2/21/2025 **Status:** ✅ Merged **Merged:** 2/22/2025 **Merged by:** [@bmizerany](https://github.com/bmizerany) **Base:** `main` ← **Head:** `bmizerany/regrouproutes` --- ### 📝 Commits (3) - [`2aa076b`](https://github.com/ollama/ollama/commit/2aa076bc62743078a426c4fd25071ea3b188ebba) server: group routes by category and purpose - [`4015179`](https://github.com/ollama/ollama/commit/4015179c9695dee9b7f38cc47bf2289b0800d90a) Update routes.go - [`3cfeaad`](https://github.com/ollama/ollama/commit/3cfeaad79502155e09769482a98f1f12b07a6057) cleanup GET/HEAD loop and just say GET or HEAD. ### 📊 Changes **3 files changed** (+50 additions, -32 deletions) <details> <summary>View changed files</summary> 📝 `envconfig/config.go` (+3 -3) 📝 `envconfig/config_test.go` (+1 -1) 📝 `server/routes.go` (+46 -28) </details> ### 📄 Description The route assembly in Handler lacked clear organization making it difficult scan for routes and their relationships to each other. This commit aims to fix that by reordering the assembly of routes to group them by category and purpose. Also, be more specific about what "config" refers to (it is about CORS if you were wondering... I was.) --- <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 2026-04-13 00:12:28 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
amd
api
app
bug
build
cli
cloud
compatibility
context-length
create
docker
documentation
embeddings
feature request
feedback wanted
good first issue
gpt-oss
gpu
harmony
help wanted
image
install
intel
js
launch
linux
macos
memory
mlx
model
needs more info
networking
nvidia
ollama.com
performance
pull-request
Mirrored from GitHub Pull Request
 python
question
registry
rendering
thinking
tools
top
vulkan
windows
wsl
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/ollama#12905
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?