Repository navigation
argos-dev: idea issues become epics, with spikes as their sub-issues - #35
Open
TheJeffreyKuo wants to merge 1 commit into
Open
TheJeffreyKuo wants to merge 1 commit into
TheJeffreyKuo 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.
Rewrites
create-ticketaround the ticket workflow. In GitHub, one issue carries a feature from idea to epic: every spike is a sub-issue of an idea (drafted automatically if none fits), and once settled the idea issue itself is rewritten as the epic instead of opening a separate one. Dev work hangs under its epic, if any.Follow-up outside Delphi: the Argos and Nero-2.0 issue templates and
docs/agents/issue-tracker.mdstill describe opening a separate epic and closing the idea.