docs(rules): take the highest ranked Goal your lead gives you - #136
Merged
Conversation
Time Submission Status
Submit or update total time with: Add time on top of previous submission with: See available commands to help comply with our Guidelines. |
Contributor
WalkthroughDEV-110 now directs readers to select the next Goal from their ranked Priorities issue, with a fallback for repositories without one. ChangesGoal ownership guidance
Estimated code review effort: 1 (Trivial) | ~2 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
zolotokrylin
force-pushed
the
docs/goal-priority-source
branch
from
July 30, 2026 04:00
f5d337f to
1520b85
Compare
zolotokrylin
commented
Jul 30, 2026
zolotokrylin
left a comment
Member
Author
There was a problem hiding this comment.
@holdex pr submit-time 7m
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
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.
DEV-110 told contributors to pick a Goal by their own read of impact and urgency, and to ask their lead if unsure. For anyone working across several repos that is a guess, and it ignores that a lead may already have decided the order.
The rule now takes the ranked order as the answer where one is given, and keeps the impact-and-urgency fallback for contributors who have none. It says nothing about where that order is kept, which is deliberate: that is the lead's business, not the contribution model's.