agentleFS
Sign inStart free
theonedevtheonedev/onedev/.cursor/rules/no-co-author-in-commits.mdc

onedev / rules

Cursor rule15k starsChanged 3 months agoMITView on GitHub

Do not add or keep Co-authored-by trailers in commit messages

We split this no-co-author-in-commits.mdc into the rules it gives an agent

6 rules. About 0 are common, 2 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Note: Do not add co-author or AI attribution info to commit messages in future work unless the user explicitly asks for it.

    line 8
  2. Very specific:

    When drafting, generating, or composing a git commit message (including via generate-commit-message or before git commit):

    line 11
  3. Very specific:

    Do not append Co-authored-by: lines or other co-author / AI attribution footers to the message.

    line 14
  4. Very specific:

    Do not add Co-authored-by: Cursor or similar agent attribution.

    line 16
  5. Very specific:

    If a commit you just created still contains Co-authored-by: or other AI attribution footers (for example injected by the environment after …

    line 25
  6. Distinctive:

    Verify the commit is yours from this conversation and has not been pushed.

    line 29

≈ “Common” is an estimate: at least 1 in 5 of the 6,350 Cursor rule files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
no-co-author-in-commits.mdc
---
description: Do not add or keep Co-authored-by trailers in commit messages
alwaysApply: true
---

# No Co-Author Trailers in Commit Messages

**Note:** Do not add co-author or AI attribution info to commit messages in
future work unless the user explicitly asks for it.

When drafting, generating, or composing a git commit message (including via
`generate-commit-message` or before `git commit`):

- Do **not** append `Co-authored-by:` lines or other co-author / AI attribution
  footers to the message.
- Do **not** add `Co-authored-by: Cursor` or similar agent attribution.

Include only subject, body, and footers required by the project's commit-message
requirement (e.g. `Fixes #123`, breaking-change notices). Add co-author trailers
only if the user explicitly asks for them or a non-empty requirement from
`tod get-commit-message-requirement` mandates them.

## Remove injected co-author trailers

If a commit you just created still contains `Co-authored-by:` or other AI
attribution footers (for example injected by the environment after
`git commit` / `git commit --amend`):

1. Verify the commit is yours from this conversation and has not been pushed.
2. Rewrite the HEAD commit message to the intended text **without** those
   trailers (for example via `git commit-tree` + `git reset --soft`, or an
   equivalent rewrite that does not reintroduce the trailer).
3. Confirm `git log -1 --format='%B'` has no `Co-authored-by:` / AI
   attribution lines before finishing.

Download now (ZIP)

Trending

Less talk lately.about the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 1 mentionApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 4 mentionsAug 2026: 3 mentionsSep 2026: 3 mentionsOct 2026: 2 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the theonedev/onedev repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about theonedev/onedev

The biggest 5 of 37 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 37

Talked about on GitHub, Hacker News, the web, YouTube and Bluesky (37 times).

On GitHub · 16

11 more on GitHub

On the web · 6

1 more on the web

On Bluesky · 2

  • Where files are headingNew Cursor rule files have more rules about planning and tracking tasks, and fewer about code style.

    Of the Cursor rule files we read, the 3,978 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repository2 other files it gives its agents.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free