From 6e92a4358a51a4572f44617bac152925b516021c Mon Sep 17 00:00:00 2001 From: Mads Lorentzen <50207393+MadsLorentzen@users.noreply.github.com> Date: Thu, 9 Jul 2026 06:10:16 +0200 Subject: [PATCH] docs: add credit norm to CONTRIBUTING.md (#89) Co-authored-by for incorporated code; named commit/PR mention for independently written fixes derived from reports. Prompted by the question in #66. Co-authored-by: Claude Fable 5 --- CONTRIBUTING.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 104b0a3..466697c 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -35,6 +35,8 @@ Reviews here are empirical. Bug reports are reproduced on master before the fix - Put CLI tests in `.agents/skills//cli/tests/` (bun test, network-free where possible); Python tool tests in `tests/`. - Run what CI runs: `python3 tools/lint_skills.py` (or `python tools/lint_skills.py` if that is your Python 3 executable), `bun run typecheck` in touched CLIs, and the relevant test suites. +**Credit norm:** a change that incorporates your actual code gets a `Co-authored-by` trailer; a change written independently from your observation or report gets a named mention in the commit message and PR. Both happen unprompted. + ## Building for your own market? Do this instead 1. Fork the repo and run `/add-portal` with your local job board - it scaffolds a portal skill matching the shipped contract, and `/scrape` picks it up automatically.