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
Currently this action only says "you got something wrong" and it leaves it up to you to figure out what. It would nice if it would report what part of the spec it's complaining about.
Like if the PR title is disable a flaky test it would be nice if the action somewhere listed that it's in violation because it's missing the <type>: prefix instead of leaving it up to the user to guess about what's not right.
The text was updated successfully, but these errors were encountered:
The way the check is structured, in general, is to see if the title matches at least one template out of the many specified (via regex and/or prefixes). A failing test indicates that the current title does not match any valid template. I don't see how we could give a suggestion here? I do like the idea but the only feedback I can think of is listing out all valid templates and then say that the current one does not match any of them.
Currently this action only says "you got something wrong" and it leaves it up to you to figure out what. It would nice if it would report what part of the spec it's complaining about.
Like if the PR title is
disable a flaky test
it would be nice if the action somewhere listed that it's in violation because it's missing the<type>:
prefix instead of leaving it up to the user to guess about what's not right.The text was updated successfully, but these errors were encountered: