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

[PR #9405] [MERGED] CONTRIBUTING: clarify commit message guidelines and add examples #12951

New Issue
Closed
opened 2026-04-13 00:13:36 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-13 00:13:36 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/ollama/ollama/pull/9405
Author: @bmizerany
Created: 2/27/2025
Status: ✅ Merged
Merged: 2/28/2025
Merged by: @bmizerany

Base: main ← Head: bmizerany/fixcommitmessageguide

📝 Commits (1)

  • 3fe3feb CONTRIBUTING: provide clarity on good commit messages, and bad

📊 Changes

1 file changed (+57 additions, -6 deletions)

View changed files

📝 CONTRIBUTING.md (+57 -6)

📄 Description

Also, our commit messages have been getting better, but we can do better, and be more consistent. This adds more clarity on how to write commit messages and provides examples of good and bad messages.

Also, our contributing guide was lacking helpful guidance on how to start change proposals. This commit adds the start of that section.

Soon, we should add a proposal template to the issue tracker with a link back to the proposal section, which should also be expanded upon.

🔄 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/9405 **Author:** [@bmizerany](https://github.com/bmizerany) **Created:** 2/27/2025 **Status:** ✅ Merged **Merged:** 2/28/2025 **Merged by:** [@bmizerany](https://github.com/bmizerany) **Base:** `main` ← **Head:** `bmizerany/fixcommitmessageguide` --- ### 📝 Commits (1) - [`3fe3feb`](https://github.com/ollama/ollama/commit/3fe3feb3da289ebf24fe4a73a3fe39feae6d755a) CONTRIBUTING: provide clarity on good commit messages, and bad ### 📊 Changes **1 file changed** (+57 additions, -6 deletions) <details> <summary>View changed files</summary> 📝 `CONTRIBUTING.md` (+57 -6) </details> ### 📄 Description Also, our commit messages have been getting better, but we can do better, and be more consistent. This adds more clarity on how to write commit messages and provides examples of good and bad messages. Also, our contributing guide was lacking helpful guidance on how to start change proposals. This commit adds the start of that section. Soon, we should add a proposal template to the issue tracker with a link back to the proposal section, which should also be expanded upon. --- <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-13 00:13:36 -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#12951
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?