[PR #206] [MERGED] docs: use conventional commit titles with the area as scope #205

New issue

Closed

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

bsakaguchi commented

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

Owner

📋 Pull Request Information

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

Base: main ← Head: docs/conventional-commit-titles

📝 Commits (1)

f272a9d docs: use conventional commit titles with the area as scope

📊 Changes

2 files changed (+8 additions, -6 deletions)

View changed files

📝 .github/pull_request_template.md (+1 -1)
📝 CONTRIBUTING.md (+7 -5)

📄 Description

📝 Summary

Commit and PR titles go back to Conventional Commits, with the area of the project as the scope: feat(cli): add --config to point at a config file.

🔧 What changes

CONTRIBUTING.md: the Commit Messages section shows type(area): description with examples, the list of types and the list of areas. The area can be skipped when a change has none.
PR template: the title hint uses the new format.
Release PRs keep chore: release vX.Y.Z from task release, it already fits.

✅ 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/206 **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/conventional-commit-titles` --- ### 📝 Commits (1) - [`f272a9d`](https://github.com/Glitchy-Sheep/boosty-downloader/commit/f272a9d809b6064eb4d2707b36794880f249d279) docs: use conventional commit titles with the area as scope ### 📊 Changes **2 files changed** (+8 additions, -6 deletions) <details> <summary>View changed files</summary> 📝 `.github/pull_request_template.md` (+1 -1) 📝 `CONTRIBUTING.md` (+7 -5) </details> ### 📄 Description ## 📝 Summary Commit and PR titles go back to Conventional Commits, with the area of the project as the scope: `feat(cli): add --config to point at a config file`. ## 🔧 What changes - CONTRIBUTING.md: the Commit Messages section shows `type(area): description` with examples, the list of types and the list of areas. The area can be skipped when a change has none. - PR template: the title hint uses the new format. - Release PRs keep `chore: release vX.Y.Z` from `task release`, it already fits. ## ✅ 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:49 +00:00