-
Notifications
You must be signed in to change notification settings - Fork 77
support 2026 "all year goals" #428
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Introduce a new goal format for 2026+ that replaces the detailed "Ownership and team asks" table with a simpler "Team asks" section using support levels (Vibes, Small, Medium, Large). Key changes: - Add TeamSupport, SupportLevel, and TeamInvolvement types to handle both old and new formats - Parse "Team asks" section with Team/Support level/Notes columns - Add format_team_support module for rendering new format tables - Update all consumers to use TeamInvolvement abstraction - Update 2026 README with new support level definitions - Backwards compatible: old format goals still work 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <[email protected]>
Reflects the shift from half-year (YYYYHN) to yearly (YYYY) goal planning and replaces detailed activity definitions with the new tiered support model (Vibes/Small/Medium/Large). 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <[email protected]>
…ing dated sections New goal process sections are now inserted before the first existing dated section (⏳ or ⚙️) rather than after # Summary. This keeps the Introduction link at the top and groups all goal process sections together. Also adds support for year-only timeframes (e.g., 2027) without H1/H2 suffix. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <[email protected]>
|
Error: The feature Please file an issue on GitHub at triagebot if there's a problem with this bot, or reach out on #triagebot on Zulip. |
| > * *Example:* A compiler change that will require a few small PRs to be reviewed. | ||
| > * *Example:* Asking the lang team to approve a lint. | ||
| > * Medium: You need dedicated support from one person, but the rest of the team doesn't have to do much. | ||
| > * *Example:* A compiler change that doesn't require any rearchitecting but |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
stray "but", looks like we're missing something here
r? @tomassedovic
Rendered