Workflow input and output text fixes#131
Merged
Merged
Conversation
In IssueLabeler/src/Tester/Tester.cs, the AlertType decision uses
stats.MismatchesPercentage < 0.15f
to render the green Note banner (vs the yellow Warning banner) for the
'finished testing' summary. The Tip alert rendered immediately below
that banner, however, told the reader the favorable threshold was
'less than 10%'. A run with, say, 13% mismatches would land on a green
'favorable' banner sitting right next to a Tip claiming favorability
required less than 10% mismatches — leaving the reader unsure which
piece of UI to trust.
Update the Tip text to 'less than 15%' so it matches the decision the
code actually makes. No behavioural change: any run that rendered green
before still renders green; any run that rendered yellow before still
renders yellow. Only the help text changes.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
The promote and predict actions, the cache-retention workflow's matrix, and Predictor/Args.cs all order the three supported content types as (issues, pulls, discussions). The download, restore, test, train, and labeler-train action/workflow files inconsistently used (issues, discussions, pulls). Standardize on the canonical (issues, pulls, discussions) order across all action.yml files and the labeler-train.yml workflow: * download/action.yml, restore/action.yml, test/action.yml, train/action.yml: input descriptions, bash validation conditions, error messages, step-summary text, and step-summary ternary fallthroughs. * .github/workflows/labeler-train.yml: workflow header comment, type input description, and the workflow_dispatch type choice options (now All, Issues, Pull Requests, Discussions). No behavior changes. The set of accepted/rejected values is unchanged. The ternary fallthroughs ( ype == 'issues' && 'Issues' || type == 'pulls' && 'Pull Requests' || 'Discussions') produce identical output for every accepted input. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
github-actions
Bot
added
the
area-Workflows
Contributor
There was a problem hiding this comment.
Pull request overview
This PR standardizes the user-facing text in composite actions and the training workflow so that input descriptions, validation errors, and summaries consistently refer to model/data types in the same order (Issues, Pull Requests, Discussions). It also aligns the Tester summary guidance with the actual “favorable” threshold used by the code.
Changes:
- Reordered
typeinput descriptions and validation error/summary text across Train/Test/Restore/Download composite actions. - Reordered the
workflow_dispatchchoice options/descriptions in the training workflow for consistent presentation. - Updated the Tester summary tip to match the existing 15% mismatches threshold used for result alerting.
Reviewed changes
Copilot reviewed 6 out of 6 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| train/action.yml | Aligns descriptions, validation errors, and summary text ordering for model training inputs/outputs. |
| test/action.yml | Aligns descriptions and validation error text ordering for model testing input. |
| restore/action.yml | Aligns restore action input description, validation errors, and summary text ordering. |
| download/action.yml | Aligns descriptions, validation errors, and summary text ordering for data download outputs. |
| IssueLabeler/src/Tester/Tester.cs | Makes the summary “favorable” guidance consistent with the 0.15 mismatches threshold used in logic. |
| .github/workflows/labeler-train.yml | Reorders workflow dispatch choice descriptions/options for consistent UI text. |
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.
No description provided.