Skip to content

Autonomous development for real products. Governed agents build from specs you approve, follow the rules you set, and nothing merges until another agent proves it. Your decisions, judgement and taste are the bar that work must clear. Declare your vision and let agents build it.

docs(contributing): clarify issue and pull request guidance [I1]

Corey Olson7deafae59782
diff --git a/.github/ISSUE_TEMPLATE/feature_request.md b/.github/ISSUE_TEMPLATE/feature_request.md
index 1a267e86..7ce72dbd 100644
--- a/.github/ISSUE_TEMPLATE/feature_request.md
+++ b/.github/ISSUE_TEMPLATE/feature_request.md
@@ -2,7 +2,7 @@
name: Feature request
about: Describe a problem Pullboard could solve
title: ""
-labels: enhancement
+labels: feature
assignees: ""
---
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 435157a0..237dbe7e 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -8,6 +8,24 @@ Thanks for helping. Pullboard is MIT-licensed.
- **Pull requests are welcome too.** Every one goes through the same checks as the work Pullboard's own agents do, and nothing skips them.
- **Two quick steps for your first pull request:** agree to our Contributor License Agreement (one click, once) and sign off each commit (one flag). Both are explained below.
+## Issues and pull requests
+
+These are aims, not promises.
+
+**Issues**
+- We aim to have a first reply within 7 days.
+- Labelled `bug`, `feature`, `question` or `docs`.
+- `clarify`: closes after 14 days without a reply. Reply to reopen.
+- Confirmed issues move to our board and close; the changelog may acknowledge them.
+- Ideas and feedback in issues are welcome; Pullboard may use them freely, with no obligation. Code goes through a pull request.
+
+**Pull requests**
+- The CLA (once) and a sign-off on every commit.
+- Each one becomes a board item and is verified like any other work.
+- The relay, sealing, signing, approvals and Git hooks need the maintainer's approval.
+- `SPEC.md` changes are proposals; the maintainer approves rows.
+- Smaller is faster; large changes may be split.
+
## Licensing, the CLA and sign-off
**The Contributor License Agreement (CLA).** The first time you open a pull request, a bot asks you to agree to Pullboard's CLA with one click. You only do this once. In short:
@@ -93,7 +111,7 @@ Then use `git cs -m "..."` instead of `git commit -m "..."`.
## What happens after you open a pull request
-1. **We look at it when we can.** There is no fixed response time, and we may not reply to every pull request.
+1. **We aim to reply within 7 days.**
2. **It becomes an item on Pullboard's own board.** The bar is the behaviour your issue describes.
3. **A second reviewer checks your exact commit.** That's one of our verifier agents, plus the project owner for sensitive areas. It runs the full test suite on the minimum Node version and confirms your test fails without your change.
4. **If it passes,** it lands on `main` through our normal landing process, with you credited as the author. If we had to adjust it, you're credited as co-author with `Co-authored-by`. The pull request shows as merged, or we close it with a link to where it landed.
diff --git a/test/readme.test.js b/test/readme.test.js
index cc33d88c..9b6397e3 100644
--- a/test/readme.test.js
+++ b/test/readme.test.js
@@ -18,12 +18,19 @@ const ROOT = resolve(import.meta.dirname, '..');
const e2e = createE2eHelpers();
after(e2e.cleanup);
const README = readFileSync(join(ROOT, 'README.md'), 'utf8');
+const CONTRIBUTING = readFileSync(join(ROOT, 'CONTRIBUTING.md'), 'utf8');
const drawn = Object.keys(FIGURES).map((name) => `docs/img/${name}.svg`).sort();
const SHOT_FIGURES = [
{ path: 'docs/shots/tour.svg', alt: 'The timed Pullboard tour shows a change submitted, rejected for a missed edge, fixed and accepted.' },
{ path: 'docs/shots/desktop-light.png', alt: "The desktop board shows open, claimed, submitted and accepted work, a Needs you row for a held lane, search in the top bar, the status bar, an accepted item's review history, and a stats line with merged work, sent-back share and the bottleneck recommendation." },
];
+test('CONTRIBUTING explains issue clarification and the seven-day reply aim [I1]', () => {
+ assert.match(CONTRIBUTING, /^## Issues and pull requests$/mu, 'the contribution section is present');
+ assert.match(CONTRIBUTING, /- `clarify`: closes after 14 days without a reply\. Reply to reopen\./u, 'the clarify rule says when issues close and how to reopen them');
+ assert.match(CONTRIBUTING, /1\. \*\*We aim to reply within 7 days\.\*\*/u, 'the first reply step has the new seven-day aim');
+});
+
/**
* The dark file a README picture pairs with its light file: a PNG's `-light` becomes `-dark`, and an SVG gains `-dark`.
*