You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
BUG/MINOR: spell out expected tag formats in subject errors
When a commit subject fails the tag check, the error only named the
internal policy sets (e.g. "HAProxy Standard Patch") without saying
which tags and severity levels are valid, nor that a bare severity tag
like MINOR is also accepted. Contributors had no actionable guidance
short of reading the CONTRIBUTING link.
Now the errors list the valid tags and severity levels from the policy
config and show the expected subject prefix forms, including the
bare-scope one.
junitSuite.AddMessageFailed("", "missing tag prefix in commit message, subject must start with '<TAG>/<SEVERITY>: ' (e.g. 'BUG/MINOR: ') or a bare tag like 'MINOR: ', expected "+summary+hint, fmt.Sprintf("subject: %s", rawSubject))
195
214
slog.Error("unable to find tag match in subject", "subject", string(rawSubject))
196
215
197
-
returnfmt.Errorf("invalid tag or no tag found%s, searched through [%s]: %w",
returnfmt.Errorf("missing tag prefix in subject: subject must start with '<TAG>/<SEVERITY>: ' (e.g. 'BUG/MINOR: ') or a bare tag like 'MINOR: ', expected %s%s: %w",
0 commit comments