Rename outcomes sections for clarity#281
Merged
shaeespring merged 2 commits intomasterfrom Mar 1, 2026
Merged
Conversation
shaeespring
approved these changes
Mar 1, 2026
Contributor
shaeespring
left a comment
shaeespring
left a comment
There was a problem hiding this comment.
Lgtm! Waiting for a decision on the non-semantic-ness of the pr before merging
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
2 participants
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.
It was mislinking "outcomes listed in {Outcomes}" to the Outcomes for Membership Evals since both subsections were named Outcomes. I have renamed one to Membership Eval Outcomes and the other to Intro Eval Outcomes.
Check one:
Summary of change(s):
Both Subsections being {Outcomes} -> {Intro Eval Outcomes} and {Membership Eval Outcomes}