Issues live in the repository they concern #4

Open

marcos-mendez wants to merge 1 commit from docs/issues-per-repo into main

marcos-mendez commented

2026-09-28 00:10:33 -03:00

(Migrated from github.com)

Records as a mandatory convention what the maintainer has now had to say twice: every repository carries its own issues, and tracker is only for what is common to the whole organization.

Cross-referencing a tracker issue from a repo issue, and the reverse, stays encouraged. What is ruled out is filing repo work in tracker instead of the repo, and delegating work that exists only in a prompt rather than in an issue.

The reason is context cost: an issue next to the code it concerns can be picked up without loading the whole project.

Records as a mandatory convention what the maintainer has now had to say twice: every repository carries its own issues, and `tracker` is only for what is common to the whole organization. Cross-referencing a tracker issue from a repo issue, and the reverse, stays encouraged. What is ruled out is filing repo work in `tracker` instead of the repo, and delegating work that exists only in a prompt rather than in an issue. The reason is context cost: an issue next to the code it concerns can be picked up without loading the whole project.

marcos-mendez commented

2026-09-28 01:34:58 -03:00

(Migrated from github.com)

Reviewed with Keel-Linux/keel-core#9, Keel-Linux/common#5 and #6.

One bullet, in the section it belongs to, saying the thing the rest of this change set already does: keel-core#7 is in keel-core, common's work is in common, and tracker#6 carries only what is common to the organization. The last clause, "open the repo issue before delegating the work, never a task that exists only in a prompt", is the part with teeth and is worth having written down. It fits the surrounding list in tone and typography, and has no em dashes.

Clean above LOW: nothing to flag.

Approve

Reviewed with Keel-Linux/keel-core#9, Keel-Linux/common#5 and #6. One bullet, in the section it belongs to, saying the thing the rest of this change set already does: keel-core#7 is in keel-core, common's work is in common, and `tracker#6` carries only what is common to the organization. The last clause, "open the repo issue before delegating the work, never a task that exists only in a prompt", is the part with teeth and is worth having written down. It fits the surrounding list in tone and typography, and has no em dashes. Clean above LOW: nothing to flag. ## Approve

This pull request can be merged automatically.

This branch is out-of-date with the base branch

You are not authorized to merge this pull request.

View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.

git fetch -u origin docs/issues-per-repo:docs/issues-per-repo

git switch docs/issues-per-repo

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch main

git merge --no-ff docs/issues-per-repo

git switch docs/issues-per-repo

git rebase main

git switch main

git merge --ff-only docs/issues-per-repo

git switch docs/issues-per-repo

git rebase main

git switch main

git merge --no-ff docs/issues-per-repo

git switch main

git merge --squash docs/issues-per-repo