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

[GH-ISSUE #1807] [ISSUES] I think it would be interesting to have different templates. #63069

New Issue
Closed
opened 2026-05-03 11:38:57 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-05-03 11:38:57 -05:00
Owner
Copy Link

Originally created by @rgaidot on GitHub (Jan 5, 2024).
Original GitHub issue: https://github.com/ollama/ollama/issues/1807

Originally assigned to: @bmizerany on GitHub.

I think it would be interesting to have different templates (.github/**/*.md) for various purposes within your repo. Templates can significantly enhance efficiency and clarity in communication, especially when dealing with different aspects of your code/repo. Imagine having specific templates tailored for bug reports, allowing users to succinctly detail the issue they encountered, including steps to reproduce. This standardized format would streamline the debugging process, making it more organized and time-effective.

Similarly, having a dedicated template for reporting issues can help users express concerns or suggestions in a structured manner. Users could provide essential details, such as the nature of the problem, its impact, and any relevant markdown/screenshots, making it easier for the team to comprehend and address their concerns promptly.

Moreover, the inclusion of a feature request template could be a valuable addition. Users often have innovative ideas or specific functionalities they'd like to see implemented. A feature request template could guide users in articulating their suggestions comprehensively, specifying the intended benefits and potential use cases. This structured approach would empower your development team to better understand and evaluate the feasibility and significance of each proposed feature.

In conclusion, introducing different templates for bug reports, issue reports, and feature requests can enhance the overall user experience by promoting clear and concise communication. This, in turn, facilitates more efficient problem resolution, ensuring that your platform remains responsive to user needs and continually evolves with valuable user input.

What do you think ?

Originally created by @rgaidot on GitHub (Jan 5, 2024). Original GitHub issue: https://github.com/ollama/ollama/issues/1807 Originally assigned to: @bmizerany on GitHub. I think it would be interesting to have different templates (.github/**/*.md) for various purposes within your repo. Templates can significantly enhance efficiency and clarity in communication, especially when dealing with different aspects of your code/repo. Imagine having specific templates tailored for bug reports, allowing users to succinctly detail the issue they encountered, including steps to reproduce. This standardized format would streamline the debugging process, making it more organized and time-effective. Similarly, having a dedicated template for reporting issues can help users express concerns or suggestions in a structured manner. Users could provide essential details, such as the nature of the problem, its impact, and any relevant markdown/screenshots, making it easier for the team to comprehend and address their concerns promptly. Moreover, the inclusion of a feature request template could be a valuable addition. Users often have innovative ideas or specific functionalities they'd like to see implemented. A feature request template could guide users in articulating their suggestions comprehensively, specifying the intended benefits and potential use cases. This structured approach would empower your development team to better understand and evaluate the feasibility and significance of each proposed feature. In conclusion, introducing different templates for bug reports, issue reports, and feature requests can enhance the overall user experience by promoting clear and concise communication. This, in turn, facilitates more efficient problem resolution, ensuring that your platform remains responsive to user needs and continually evolves with valuable user input. What do you think ?
GiteaMirror commented 2026-05-03 11:38:59 -05:00
Author
Owner
Copy Link

@rgaidot commented on GitHub (Jan 5, 2024):

Templates examples


# Bug 

## Bug:  _Bug Report_

### Environment

- OS: 
- CPU:
- GPU:
- RAM:  
- (...)


## Describe
> Please provide a short summary of your bug.

### Is this a regression?
> (...)

### Reproduce

> Step

1. (...)
2. (...)

### Expected behaviour

> A clear and concise description of what you expected to happen.


# Feature

## Feature:  _Feature name/enthusiastic_

## Feature Summary

> Please provide a short summary of your changes here and any additional information that is not provided in the commit messages.

## Screenshots / Videos

> Please provide screenshots or videos.

## Definition Of Done

- [ ] Code follows the style guidelines (e.g. https://gist.github.com/rgaidot/ea5841b20505025b0284514f9adfac58)
- [ ] Checked my code and corrected any misspellings
- [ ] Changes generate no new warnings
- [ ] Test case to prove functionality
- [ ] The PR introduced no regression
- [ ] Update the documentation according to changes
<!-- gh-comment-id:1878747252 --> @rgaidot commented on GitHub (Jan 5, 2024): Templates examples --- ```md # Bug ## Bug: _Bug Report_ ### Environment - OS: - CPU: - GPU: - RAM: - (...) ## Describe > Please provide a short summary of your bug. ### Is this a regression? > (...) ### Reproduce > Step 1. (...) 2. (...) ### Expected behaviour > A clear and concise description of what you expected to happen. ``` --- ```md # Feature ## Feature: _Feature name/enthusiastic_ ## Feature Summary > Please provide a short summary of your changes here and any additional information that is not provided in the commit messages. ## Screenshots / Videos > Please provide screenshots or videos. ## Definition Of Done - [ ] Code follows the style guidelines (e.g. https://gist.github.com/rgaidot/ea5841b20505025b0284514f9adfac58) - [ ] Checked my code and corrected any misspellings - [ ] Changes generate no new warnings - [ ] Test case to prove functionality - [ ] The PR introduced no regression - [ ] Update the documentation according to changes ```
GiteaMirror commented 2026-05-03 11:38:59 -05:00
Author
Owner
Copy Link

@bmizerany commented on GitHub (Mar 14, 2024):

Ask and you shall receive! https://github.com/ollama/ollama/issues/new/choose

<!-- gh-comment-id:1998602354 --> @bmizerany commented on GitHub (Mar 14, 2024): Ask and you shall receive! https://github.com/ollama/ollama/issues/new/choose
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#63069
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?