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
Noone is actually fully adhering to what the PR template asks of PRs. It asks twice for the associated issue and if the PR is a breaking change, and suggests a naming scheme that doesn't reflect the lived reality.
I think it can be condensed to something much shorter, and if we really want to follow conventional commits for PR titles, as the template suggests, we should make that a criteria for code review. Or just drop it from the template if not.
The text was updated successfully, but these errors were encountered:
Noone is actually fully adhering to what the PR template asks of PRs. It asks twice for the associated issue and if the PR is a breaking change, and suggests a naming scheme that doesn't reflect the lived reality.
I think it can be condensed to something much shorter, and if we really want to follow conventional commits for PR titles, as the template suggests, we should make that a criteria for code review. Or just drop it from the template if not.
The text was updated successfully, but these errors were encountered: