Repository navigation
Issues live in the repository they concern - #4
Open
marcos-mendez wants to merge 1 commit into
Open
marcos-mendez wants to merge 1 commit into
marcos-mendez wants to merge 1 commit into
Conversation
The tracker repo is for what is common to the whole organization. Work that lands in a repository gets an issue there and is closed by a pull request there, so the project's memory stays next to the code it concerns and neither a person nor an agent has to load the whole project to work on one repo. Recorded as a mandatory convention because it has had to be corrected twice.
Contributor
Author
|
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 Clean above LOW: nothing to flag. Approve |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Records as a mandatory convention what the maintainer has now had to say twice: every repository carries its own issues, and
trackeris 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
trackerinstead 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.