[PR #205] [MERGED] [docs] Describe the [area] title format for commits and PRs #203

New issue

Closed

opened 2026-10-13 19:48:48 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-13 19:48:48 +00:00

Owner

📋 Pull Request Information

Original PR: https://github.com/Glitchy-Sheep/boosty-downloader/pull/205
Author: @Glitchy-Sheep
Created: 9/22/2026
Status: ✅ Merged
Merged: 9/22/2026
Merged by: @Glitchy-Sheep

Base: main ← Head: docs/commit-title-format

📝 Commits (1)

a9b0090 [docs] Describe the [area] title format for commits and PRs

📊 Changes

1 file changed (+8 additions, -4 deletions)

View changed files

📝 CONTRIBUTING.md (+8 -4)

📄 Description

📝 Summary

CONTRIBUTING.md now describes the title format the repo really uses: [area] Imperative sentence, not Conventional Commits.

🔧 What changes

The Commit Messages section explains that PRs are squash-merged, so the PR title becomes the commit on main.
It shows the [area] Imperative sentence format with real titles and lists the common areas.
Release PRs keep the chore: release vX.Y.Z title from task release.
It links the PR template.

💡 Why

All recent PRs use [area] ... titles. The guide still asked for feat: / fix:, so new contributors and agents got the wrong format.

✅ Checklist

Tested live on a real blog (feature or fix)
Updated CLI --help and README if needed
Updated docs/ if the download flow or dev process changed
Added a line to ## Unreleased in CHANGELOG.md (or the ci/skip-changelog label if not user-facing)

_{🔄 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/Glitchy-Sheep/boosty-downloader/pull/205 **Author:** [@Glitchy-Sheep](https://github.com/Glitchy-Sheep) **Created:** 9/22/2026 **Status:** ✅ Merged **Merged:** 9/22/2026 **Merged by:** [@Glitchy-Sheep](https://github.com/Glitchy-Sheep) **Base:** `main` ← **Head:** `docs/commit-title-format` --- ### 📝 Commits (1) - [`a9b0090`](https://github.com/Glitchy-Sheep/boosty-downloader/commit/a9b0090100a879bf4638f2dd771193596646dd47) [docs] Describe the [area] title format for commits and PRs ### 📊 Changes **1 file changed** (+8 additions, -4 deletions) <details> <summary>View changed files</summary> 📝 `CONTRIBUTING.md` (+8 -4) </details> ### 📄 Description ## 📝 Summary CONTRIBUTING.md now describes the title format the repo really uses: `[area] Imperative sentence`, not Conventional Commits. ## 🔧 What changes - The Commit Messages section explains that PRs are squash-merged, so the PR title becomes the commit on `main`. - It shows the `[area] Imperative sentence` format with real titles and lists the common areas. - Release PRs keep the `chore: release vX.Y.Z` title from `task release`. - It links the PR template. ## 💡 Why All recent PRs use `[area] ...` titles. The guide still asked for `feat:` / `fix:`, so new contributors and agents got the wrong format. ## ✅ Checklist  - [x] Tested live on a real blog (feature or fix) - [x] Updated CLI `--help` and README if needed - [x] Updated `docs/` if the download flow or dev process changed - [x] Added a line to `## Unreleased` in CHANGELOG.md (or the `ci/skip-changelog` label if not user-facing) --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

bsakaguchi

2026-10-13 19:48:48 +00:00