Let issues start like conversations, with natural @mentions - #6
Draft
blackboxprogramming wants to merge 1 commit into
Draft
blackboxprogramming wants to merge 1 commit into
blackboxprogramming wants to merge 1 commit into
Conversation
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.
People should be able to begin a repo conversation with a rough question such as “yo, not sure why this broke,” then add details through replies.
This adds:
This is part of the shared RoadOS conversation work: https://github.com/blackboxprogramming/RoadOS/pull/14. The scrolling viewer remains in RoadOS. This PR adds the repository convention and starter only; it does not post comments, dispatch agents, or change GitHub's interface.
Validation: inspected the current repository tree for applicable instructions and existing templates; added two new Markdown files without replacing existing content; read both files back from the new commit and confirmed exact content. No runtime code changed, so no runtime tests were needed. The template becomes available after merging into the default branch.