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

[GH-ISSUE #5518] Ollama-kis new model #3447

New Issue
Closed
opened 2026-04-12 14:07:07 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-04-12 14:07:07 -05:00
Owner
Copy Link

Originally created by @elearningshow on GitHub (Jul 6, 2024).
Original GitHub issue: https://github.com/ollama/ollama/issues/5518

How do you get your GUI listed in Community Integrations, Web & Desktop? https://github.com/elearningshow/ollama-kis

Originally created by @elearningshow on GitHub (Jul 6, 2024). Original GitHub issue: https://github.com/ollama/ollama/issues/5518 How do you get your GUI listed in Community Integrations, Web & Desktop? https://github.com/elearningshow/ollama-kis
GiteaMirror added the model label 2026-04-12 14:07:07 -05:00
GiteaMirror commented 2026-04-12 14:07:09 -05:00
Author
Owner
Copy Link

@mchiang0610 commented on GitHub (Jul 9, 2024):

Thanks. Possible to do a pull request?

<!-- gh-comment-id:2216501113 --> @mchiang0610 commented on GitHub (Jul 9, 2024): Thanks. Possible to do a pull request?
GiteaMirror commented 2026-04-12 14:07:10 -05:00
Author
Owner
Copy Link

@elearningshow commented on GitHub (Jul 9, 2024):

Thank you for your reply mchiang0610, I have not done this before and not sure of the steps. Since it is not a change to the content and rather just a link to a new Community Integrations, Web & Desktop. Not sure what to do? Chatgpt, suggests the following (Fork the Repository: Start by forking the Ollama repository on GitHub to have your own copy to work with.
Create a Branch: Create a new branch in your forked repository for your changes.
Make Your Changes: Add your integration details to the relevant section of the documentation or README file. Ensure you follow the formatting and contribution guidelines provided by the Ollama repository.
Commit Your Changes: Commit your changes with a clear and descriptive commit message.
Open a Pull Request: Open a pull request (PR) to the main Ollama repository. In the PR description, explain your integration and why it should be included in the Community Integrations section. Reference any relevant documentation or examples that highlight the functionality of your integration.
Review Process: Wait for the maintainers of the Ollama repository to review your PR. They may request changes or provide feedback that you will need to address before the PR is merged.) but these instructions are not working for me.

<!-- gh-comment-id:2217962815 --> @elearningshow commented on GitHub (Jul 9, 2024): Thank you for your reply mchiang0610, I have not done this before and not sure of the steps. Since it is not a change to the content and rather just a link to a new Community Integrations, Web & Desktop. Not sure what to do? Chatgpt, suggests the following (Fork the Repository: Start by forking the Ollama repository on GitHub to have your own copy to work with. Create a Branch: Create a new branch in your forked repository for your changes. Make Your Changes: Add your integration details to the relevant section of the documentation or README file. Ensure you follow the formatting and contribution guidelines provided by the Ollama repository. Commit Your Changes: Commit your changes with a clear and descriptive commit message. Open a Pull Request: Open a pull request (PR) to the main Ollama repository. In the PR description, explain your integration and why it should be included in the Community Integrations section. Reference any relevant documentation or examples that highlight the functionality of your integration. Review Process: Wait for the maintainers of the Ollama repository to review your PR. They may request changes or provide feedback that you will need to address before the PR is merged.) but these instructions are not working for me.
GiteaMirror commented 2026-04-12 14:07:11 -05:00
Author
Owner
Copy Link

@elearningshow commented on GitHub (Jul 9, 2024):

I believe this maybe the correct structure for a pull request to be added into the Community Integration, Web & Desktop section - https://github.com/ollama/ollama/pull/5575

<!-- gh-comment-id:2217991254 --> @elearningshow commented on GitHub (Jul 9, 2024): I believe this maybe the correct structure for a pull request to be added into the Community Integration, Web & Desktop section - https://github.com/ollama/ollama/pull/5575
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 model
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#3447
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?