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

[GH-ISSUE #15675] docs: redeploy-ready canonical docs cleanup is blocked by upstream permissions #87688

New Issue
Closed
opened 2026-05-10 06:14:46 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-05-10 06:14:46 -05:00
Owner
Copy Link

Originally created by @PureBlissAK on GitHub (Apr 18, 2026).
Original GitHub issue: https://github.com/ollama/ollama/issues/15675

Canonical target-server-local docs and host-profile cleanup are complete locally and validated.

State:

  • Local branch: main is ahead of origin/main by 2 commits
  • Published fork branch: PureBlissAK/ollama@main at cb6081ea145319e59b5e522d01530bf3208eae0f
  • Validation: git diff --check, bash -n on touched shell scripts, python3 -m py_compile on touched Python scripts, ./scripts/host-profile-matrix.sh --no-open-issue

Blocker:

  • Direct push to ollama/ollama main is denied for the current token
  • GitHub PR creation from the fork branch to ollama/ollama main failed with 'no history in common'

Requested next step:

  • Mirror or cherry-pick the published fork main branch into ollama/ollama main so the redeploy path can complete.

Published branch should be treated as the validated handoff point for the on-prem documentation and deployment cleanup.

Originally created by @PureBlissAK on GitHub (Apr 18, 2026). Original GitHub issue: https://github.com/ollama/ollama/issues/15675 Canonical target-server-local docs and host-profile cleanup are complete locally and validated. State: - Local branch: main is ahead of origin/main by 2 commits - Published fork branch: PureBlissAK/ollama@main at cb6081ea145319e59b5e522d01530bf3208eae0f - Validation: git diff --check, bash -n on touched shell scripts, python3 -m py_compile on touched Python scripts, ./scripts/host-profile-matrix.sh --no-open-issue Blocker: - Direct push to ollama/ollama main is denied for the current token - GitHub PR creation from the fork branch to ollama/ollama main failed with 'no history in common' Requested next step: - Mirror or cherry-pick the published fork main branch into ollama/ollama main so the redeploy path can complete. Published branch should be treated as the validated handoff point for the on-prem documentation and deployment cleanup.
GiteaMirror commented 2026-05-10 06:14:47 -05:00
Author
Owner
Copy Link

@PureBlissAK commented on GitHub (Apr 18, 2026):

Resolved by PR #15676, which replays the validated target-server-local documentation cleanup onto a branch based on ollama/ollama:main. The fork handoff and redeploy path are now tracked by the open PR.

<!-- gh-comment-id:4274160696 --> @PureBlissAK commented on GitHub (Apr 18, 2026): Resolved by PR #15676, which replays the validated target-server-local documentation cleanup onto a branch based on ollama/ollama:main. The fork handoff and redeploy path are now tracked by the open PR.
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
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#87688
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?