Instructions to use Tavernari/Qwen2.5-Coder-1.5B-git-commit-message-reasoning-GGUF with libraries, inference providers, notebooks, and local apps. Follow these links to get started.

Notebooks
Google Colab
Kaggle
Local Apps Settings

How to use Tavernari/Qwen2.5-Coder-1.5B-git-commit-message-reasoning-GGUF with llama.cpp:

Install (macOS, Linux)

curl -LsSf https://llama.app/install.sh | sh
# Start a local OpenAI-compatible server with a web UI:
llama serve -hf Tavernari/Qwen2.5-Coder-1.5B-git-commit-message-reasoning-GGUF:Q4_K_M
# Run inference directly in the terminal:
llama cli -hf Tavernari/Qwen2.5-Coder-1.5B-git-commit-message-reasoning-GGUF:Q4_K_M

Install from WinGet (Windows)

winget install llama.cpp
# Start a local OpenAI-compatible server with a web UI:
llama serve -hf Tavernari/Qwen2.5-Coder-1.5B-git-commit-message-reasoning-GGUF:Q4_K_M
# Run inference directly in the terminal:
llama cli -hf Tavernari/Qwen2.5-Coder-1.5B-git-commit-message-reasoning-GGUF:Q4_K_M

Build from source code

git clone https://github.com/ggml-org/llama.cpp.git
cd llama.cpp
cmake -B build
cmake --build build -j --target llama-app
# Start a local OpenAI-compatible server with a web UI:
./build/bin/llama serve -hf Tavernari/Qwen2.5-Coder-1.5B-git-commit-message-reasoning-GGUF:Q4_K_M
# Run inference directly in the terminal:
./build/bin/llama cli -hf Tavernari/Qwen2.5-Coder-1.5B-git-commit-message-reasoning-GGUF:Q4_K_M

Use Docker

docker model run hf.co/Tavernari/Qwen2.5-Coder-1.5B-git-commit-message-reasoning-GGUF:Q4_K_M

Llama new
LM Studio
Jan
Ollama
How to use Tavernari/Qwen2.5-Coder-1.5B-git-commit-message-reasoning-GGUF with Ollama:
```
ollama run hf.co/Tavernari/Qwen2.5-Coder-1.5B-git-commit-message-reasoning-GGUF:Q4_K_M
```
Unsloth Desktop

How to use Tavernari/Qwen2.5-Coder-1.5B-git-commit-message-reasoning-GGUF with Pi:

Start the llama.cpp server

# Install llama.cpp:
brew install llama.cpp
# Start a local OpenAI-compatible server:
llama serve -hf Tavernari/Qwen2.5-Coder-1.5B-git-commit-message-reasoning-GGUF:Q4_K_M

Configure the model in Pi

# Install Pi:
npm install -g @earendil-works/pi-coding-agent
# Add to ~/.pi/agent/models.json:
{
  "providers": {
    "llama-cpp": {
      "baseUrl": "http://localhost:8080/v1",
      "api": "openai-completions",
      "apiKey": "none",
      "models": [
        {
          "id": "Tavernari/Qwen2.5-Coder-1.5B-git-commit-message-reasoning-GGUF:Q4_K_M"
        }
      ]
    }
  }
}

Run Pi

# Start Pi in your project directory:
pi

Docker Model Runner
How to use Tavernari/Qwen2.5-Coder-1.5B-git-commit-message-reasoning-GGUF with Docker Model Runner:
```
docker model run hf.co/Tavernari/Qwen2.5-Coder-1.5B-git-commit-message-reasoning-GGUF:Q4_K_M
```

Lemonade

How to use Tavernari/Qwen2.5-Coder-1.5B-git-commit-message-reasoning-GGUF with Lemonade:

Pull the model

# Download Lemonade from https://lemonade-server.ai/
lemonade pull Tavernari/Qwen2.5-Coder-1.5B-git-commit-message-reasoning-GGUF:Q4_K_M

Run and chat with the model

lemonade run user.Qwen2.5-Coder-1.5B-git-commit-message-reasoning-GGUF-Q4_K_M

List all available models

lemonade list

Hermes Agent

How to use Tavernari/Qwen2.5-Coder-1.5B-git-commit-message-reasoning-GGUF with Hermes Agent:

Start the llama.cpp server

# Install llama.cpp:
brew install llama.cpp
# Start a local OpenAI-compatible server:
llama serve -hf Tavernari/Qwen2.5-Coder-1.5B-git-commit-message-reasoning-GGUF:Q4_K_M

Configure Hermes

# Install Hermes:
curl -fsSL https://hermes-agent.nousresearch.com/install.sh | bash
hermes setup
# Point Hermes at the local server:
hermes config set model.provider custom
hermes config set model.base_url http://127.0.0.1:8080/v1
hermes config set model.default Tavernari/Qwen2.5-Coder-1.5B-git-commit-message-reasoning-GGUF:Q4_K_M

Run Hermes

hermes

Atomic Chat

OpenClaw

How to use Tavernari/Qwen2.5-Coder-1.5B-git-commit-message-reasoning-GGUF with OpenClaw:

Start the llama.cpp server

# Install llama.cpp:
brew install llama.cpp
# Start a local OpenAI-compatible server:
llama serve -hf Tavernari/Qwen2.5-Coder-1.5B-git-commit-message-reasoning-GGUF:Q4_K_M

Configure OpenClaw

# Install OpenClaw:
npm install -g openclaw@latest
# Register the local server and set it as the default model:
openclaw onboard --non-interactive --mode local \
  --auth-choice custom-api-key \
  --custom-base-url http://127.0.0.1:8080/v1 \
  --custom-model-id "Tavernari/Qwen2.5-Coder-1.5B-git-commit-message-reasoning-GGUF:Q4_K_M" \
  --custom-provider-id llama-cpp \
  --custom-compatibility openai \
  --custom-text-input \
  --accept-risk \
  --skip-health

Run OpenClaw

openclaw agent --local --agent main --message "Hello from Hugging Face"

Qwen2.5-Coder-1.5B-git-commit-message-reasoning-GGUF / Modelfile

Tavernari

Upload Modelfile

3d4d15e verified over 1 year ago

Raw History Blame Contribute Delete

1.94 kB

**Instruction to the model:**
1. You have been given a git diff (code changes).
2. You must analyze it and generate a concise, informative commit message.
3. The final output must have two parts:
   - A `<think>` block containing your internal reasoning written as if you are a human speaking loudly and excitedly.
   - The actual **Title** and **Body** of the commit message after the `<think>` block.
4. Optionally, user can add some context to the commit message.

**Formatting Requirements:**
1. **`<think>` block**:
   - Begin with `<think>` on a single line.
   - Explain your reasoning and thought process in plain, spoken language style.
   - End with `</think>` on its own line.
   - This block is **only** for your reasoning; do not include the commit message here.

2. **Commit message**:
   - **Title**:
     - Imperative mood (e.g., "Add feature", not "Added feature").
     - Capitalize the first letter.
     - Keep the length under 50 characters.
     - No period at the end.
   - **Empty line**: Insert exactly one blank line after the title.
   - **Body**:
     - Wrap lines at 72 characters maximum.
     - Clearly explain **what changed** and **why** it was needed.
     - Finish with the tag `<!--end-->` on its own line.

**Example Output Format** (structure only):

```
<think>
[Your loud, human-style reasoning here...]
</think>
[Commit message title]
[Empty line]
[Body]
<!--end-->
```

---

**Your task**:
1. Examine the provided git diff (the changes to the code).
2. Start your response with a `<think>` block containing your reasoning.
3. After `</think>`, provide the commit message title on one line.
4. Leave exactly one empty line.
5. Provide the commit message body, wrapping lines at 72 characters, and ending with `<!--end-->`.
6. Never start commit with Title: or Body: or anything else, just the commit message.

That’s it! Follow these rules strictly to ensure the commit message is properly formatted.

	Instruction to the model:
	1. You have been given a git diff (code changes).
	2. You must analyze it and generate a concise, informative commit message.
	3. The final output must have two parts:
	- A `<think>` block containing your internal reasoning written as if you are a human speaking loudly and excitedly.
	- The actual Title and Body of the commit message after the `<think>` block.
	4. Optionally, user can add some context to the commit message.

	Formatting Requirements:
	1. `<think>` block:
	- Begin with `<think>` on a single line.
	- Explain your reasoning and thought process in plain, spoken language style.
	- End with `</think>` on its own line.
	- This block is only for your reasoning; do not include the commit message here.

	2. Commit message:
	- Title:
	- Imperative mood (e.g., "Add feature", not "Added feature").
	- Capitalize the first letter.
	- Keep the length under 50 characters.
	- No period at the end.
	- Empty line: Insert exactly one blank line after the title.
	- Body:
	- Wrap lines at 72 characters maximum.
	- Clearly explain what changed and why it was needed.
	- Finish with the tag `<!--end-->` on its own line.

	Example Output Format (structure only):

	```
	<think>
	[Your loud, human-style reasoning here...]
	</think>
	[Commit message title]
	[Empty line]
	[Body]
	<!--end-->
	```

	---

	Your task:
	1. Examine the provided git diff (the changes to the code).
	2. Start your response with a `<think>` block containing your reasoning.
	3. After `</think>`, provide the commit message title on one line.
	4. Leave exactly one empty line.
	5. Provide the commit message body, wrapping lines at 72 characters, and ending with `<!--end-->`.
	6. Never start commit with Title: or Body: or anything else, just the commit message.

	That’s it! Follow these rules strictly to ensure the commit message is properly formatted.