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

[PR #11198] ci: add new build.yaml workflow #18746

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

📋 Pull Request Information

Original PR: https://github.com/ollama/ollama/pull/11198
Author: @mirage335
Created: 6/25/2025
Status: 🔄 Open

Base: main ← Head: build-workflow-only

📝 Commits (1)

  • 5822c21 ci: add new build.yaml workflow

📊 Changes

1 file changed (+406 additions, -0 deletions)

View changed files

➕ .github/workflows/build.yaml (+406 -0)

📄 Description

Minimal .github/workflows/build.yaml based on release.yaml to build and upload OllamaSetup.exe on 'workflow_dispatch' .

Intentionally kept similar to 'release.yaml' so it can be quickly maintained simply by side-by-side diff comparison to any newer version of 'release.yaml', etc.

Installer built in GitHub Actions CI is easier for users of their own forks to deploy to computers, preserve, etc, and sometimes more convenient for developers than getting a MSWindows build environment working locally.

Particularly handy for just creating a version of Ollama with desired changes that haven't made it to an official release (eg. 'PR 10382' , 'PR 10238' , to apparently support Llama 3.1 Nemotron Ultra 253b v1 ), or to quickly try some small change (eg. disabling automatic updates) made using OpenAI's WebUI Codex tool on a fork .

For documentation, I suggest the following (developer guide):

## Windows - GitHub Actions

Fork repository.

Navigate the GitHub WebUI to -> Actions -> build .

Click 'Run workflow' , then click the green confirmation button 'Run workflow' .

Navigate the GitHub WebUI back to the 'Code' tab of your forked repository.

Click 'Releases' on the right side panel, expand 'Assets' .

Download and install your 'OllamaSetup.exe' .

🔄 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/11198 **Author:** [@mirage335](https://github.com/mirage335) **Created:** 6/25/2025 **Status:** 🔄 Open **Base:** `main` ← **Head:** `build-workflow-only` --- ### 📝 Commits (1) - [`5822c21`](https://github.com/ollama/ollama/commit/5822c21761c8fa43e67e718010a9b97b5d29f107) ci: add new build.yaml workflow ### 📊 Changes **1 file changed** (+406 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `.github/workflows/build.yaml` (+406 -0) </details> ### 📄 Description Minimal `.github/workflows/build.yaml` based on `release.yaml` to build and upload `OllamaSetup.exe` on 'workflow_dispatch' . Intentionally kept similar to 'release.yaml' so it can be quickly maintained simply by side-by-side diff comparison to any newer version of 'release.yaml', etc. Installer built in GitHub Actions CI is easier for users of their own forks to deploy to computers, preserve, etc, and sometimes more convenient for developers than getting a MSWindows build environment working locally. Particularly handy for just creating a version of Ollama with desired changes that haven't made it to an official release (eg. '[PR 10382](https://github.com/ollama/ollama/pull/10382)' , 'PR [10238](https://github.com/ollama/ollama/pull/10238)' , to apparently support Llama 3.1 Nemotron Ultra 253b v1 ), or to quickly try some small change (eg. disabling automatic updates) made using OpenAI's WebUI Codex tool on a fork . For documentation, I suggest the following ([developer guide](https://github.com/ollama/ollama/blob/main/docs/development.md)): ```Markdown ## Windows - GitHub Actions Fork repository. Navigate the GitHub WebUI to -> Actions -> build . Click 'Run workflow' , then click the green confirmation button 'Run workflow' . Navigate the GitHub WebUI back to the 'Code' tab of your forked repository. Click 'Releases' on the right side panel, expand 'Assets' . Download and install your 'OllamaSetup.exe' . ``` --- <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:45:09 -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#18746
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?