Skip to content

fix(fix-headers): never rewrite an existing @Author - #16

Merged
Shinrai merged 2 commits into
nextfrom
fix/no-forced-author-update
Oct 4, 2026
Merged

Shinrai merged 2 commits into
nextfrom
fix/no-forced-author-update

Conversation

@cldmv-bot

@cldmv-bot cldmv-bot Bot commented Oct 4, 2026 •

Copy link
Copy Markdown
Contributor

🚀 What's Changed

💥 Breaking Changes

No breaking changes

✨ Features

No new features

🐛 Bug Fixes

📦 Dependencies

No dependency updates

🔧 Other Changes

No other changes

👥 Contributors

Drop forceAuthorUpdate from the shared config. With it on (together with
useGpgSignerAuthor), anyone who ran fix-headers in an extending repository
replaced every file's @author with their own name. @author records who
created the file, so fix-headers' default of keeping it is the right
house setting; a repository can still turn the option on for a one-off
migration.

Refs #15
@cldmv-bot cldmv-bot Bot added the type: documentation Relates to docs, README updates, guides, or inline code comments label Oct 4, 2026
Keep the option in the shared config as false instead of omitting it, so
the decision is visible and overrides anything earlier in an extends
chain.
@Shinrai
Shinrai merged commit f16e769 into next Oct 4, 2026
28 checks passed
@cldmv-bot
cldmv-bot Bot deleted the fix/no-forced-author-update branch October 4, 2026 05:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

type: documentation Relates to docs, README updates, guides, or inline code comments

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant