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

[PR #9657] [CLOSED] docs: provide clarity for accepted modelfile types and reorder Customize a Model for readability #18299

New Issue
Closed
opened 2026-04-16 06:31:16 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-16 06:31:16 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/ollama/ollama/pull/9657
Author: @Ashton-Haviland
Created: 3/11/2025
Status: ❌ Closed

Base: main ← Head: main

📝 Commits (2)

  • 96b1e43 Reordered README.md customize a model section to improve readability
  • e948e1a Added accepted file format for Modelfile

📊 Changes

1 file changed (+28 additions, -26 deletions)

View changed files

📝 README.md (+28 -26)

📄 Description

Based off of issue #9582.

Changes

  • Added line specifying ModelFile accepted file types
  • Reordered Customize a Model Section from GGUF->SafeTensor->Custom Prompt, to Custom Prompt->GGUF->SafeTensor

Reasoning

  • Improve user experience for low to mid-level users who were confused about the ambiguous format ModelFile(specifically for the creation of a new file). Heuristic Usability Testing found for heuristic 2, Match Between the System and the Real World, that there was an assumption of the users understanding of word/concept in regards to the creation of Modefiles, either using FROM/SHOW command to get a current Modefile of appropriate format, or assuming user would understand it is any simple text readable file format.
  • To improve readability and time to accomplish tasks for lower to mid-level users looking to create a custom model. The reasoning is that customizing models you already have from a file are most likely, followed by popular GGUF file format, and finally by Safetensors which Heuristic Usability testing found to be uncommon/unknown. This change would support heuristic number 8, Aesthetic and Minimalist Design by prioritizing content and features needed to support primary goals(specifically for low-mid level users).

🔄 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/9657 **Author:** [@Ashton-Haviland](https://github.com/Ashton-Haviland) **Created:** 3/11/2025 **Status:** ❌ Closed **Base:** `main` ← **Head:** `main` --- ### 📝 Commits (2) - [`96b1e43`](https://github.com/ollama/ollama/commit/96b1e433c9692374d155d89be8f5d2d7ac886369) Reordered README.md customize a model section to improve readability - [`e948e1a`](https://github.com/ollama/ollama/commit/e948e1a705cc0e22a3fd0f171bf12707f46212d9) Added accepted file format for Modelfile ### 📊 Changes **1 file changed** (+28 additions, -26 deletions) <details> <summary>View changed files</summary> 📝 `README.md` (+28 -26) </details> ### 📄 Description Based off of issue #9582. # Changes - Added line specifying ModelFile accepted file types - Reordered Customize a Model Section from GGUF->SafeTensor->Custom Prompt, to Custom Prompt->GGUF->SafeTensor # Reasoning - Improve user experience for low to mid-level users who were confused about the ambiguous format ModelFile(specifically for the creation of a new file). Heuristic Usability Testing found for heuristic 2, Match Between the System and the Real World, that there was an assumption of the users understanding of word/concept in regards to the creation of Modefiles, either using FROM/SHOW command to get a current Modefile of appropriate format, or assuming user would understand it is any simple text readable file format. - To improve readability and time to accomplish tasks for lower to mid-level users looking to create a custom model. The reasoning is that customizing models you already have from a file are most likely, followed by popular GGUF file format, and finally by Safetensors which Heuristic Usability testing found to be uncommon/unknown. This change would support heuristic number 8, Aesthetic and Minimalist Design by prioritizing content and features needed to support primary goals(specifically for low-mid level users). --- <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-16 06:31:16 -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#18299
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?