github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-07-16 05:05:37 -05:00
Code Issues 16.9k Packages Projects Releases 122 Wiki Activity

[GH-ISSUE #8077] Add support for setting models to private on ollama push #82846

New Issue
Open
opened 2026-05-09 15:56:13 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-05-09 15:56:13 -05:00
Owner
Copy Link

Originally created by @BruceMacD on GitHub (Dec 12, 2024).
Original GitHub issue: https://github.com/ollama/ollama/issues/8077

Currently, while it's possible to create private repositories through the ollama.com web interface, there's no way to initialize a new private repository directly through the ollama push CLI command. This creates friction in automated workflows and requires context switching between CLI and web interface when working with private models.

Proposed Solution

Extend the ollama push command to support creating private repositories on initialization. This would allow users to create and push to private repos in a single command.

Example usage:

ollama push username/my-model:latest --private

Justification

Enables fully automated workflows for private model management
Maintains consistency with other CLI tools (like GitHub CLI) that support private repo creation
Reduces context switching between CLI and web interface
Important for organizations that want to automate private model deployment pipelines

Alternative Solutions

  1. Status Quo: Continue requiring web interface for private repo creation
    Pro: Simpler CLI interface
    Con: Breaks automation workflows

  2. A user-level setting on ollama.com that can set new repos to automatically be private for the user.

Originally created by @BruceMacD on GitHub (Dec 12, 2024). Original GitHub issue: https://github.com/ollama/ollama/issues/8077 Currently, while it's possible to create private repositories through the ollama.com web interface, there's no way to initialize a new private repository directly through the ollama push CLI command. This creates friction in automated workflows and requires context switching between CLI and web interface when working with private models. # Proposed Solution Extend the ollama push command to support creating private repositories on initialization. This would allow users to create and push to private repos in a single command. Example usage: ```bash ollama push username/my-model:latest --private ``` # Justification Enables fully automated workflows for private model management Maintains consistency with other CLI tools (like GitHub CLI) that support private repo creation Reduces context switching between CLI and web interface Important for organizations that want to automate private model deployment pipelines # Alternative Solutions 1. Status Quo: Continue requiring web interface for private repo creation Pro: Simpler CLI interface Con: Breaks automation workflows 2. A user-level setting on ollama.com that can set new repos to automatically be private for the user.
GiteaMirror added the feature request label 2026-05-09 15:56:13 -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 feature 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#82846
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?