name	project-metadata-conventions
description	Project metadata conventions (derive author/maintainer and

Project metadata (author / repository)

Derive author and repository metadata from git config, never invent it. When you set or update author/maintainer or repository/URL fields in any manifest (Cargo.toml, pyproject.toml, package.json, Chart.yaml, README.md clone instructions, …), read the values from git:
- author: git config user.name + git config user.email → Name <email>.
- repository: git config --get remote.origin.url, normalised to the https:// form (e.g. git@github.com:owner/repo.git → https://github.com/owner/repo).
If a needed value is not configured (empty user.name / user.email, or no origin remote), ask the user for it — do not fall back to a guessed or placeholder value.

name	project-metadata-conventions
description	Project metadata conventions (derive author/maintainer and

Derive author and repository metadata from git config, never invent it. When you set or update author/maintainer or repository/URL fields in any manifest (Cargo.toml, pyproject.toml, package.json, Chart.yaml, README.md clone instructions, …), read the values from git:
- author: git config user.name + git config user.email → Name <email>.
- repository: git config --get remote.origin.url, normalised to the https:// form (e.g. git@github.com:owner/repo.git → https://github.com/owner/repo).
If a needed value is not configured (empty user.name / user.email, or no origin remote), ask the user for it — do not fall back to a guessed or placeholder value.

project-metadata-conventions