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, the verbose PR descriptions end up in the commit history by anyone using Squash and Merge on Github, which is a relatively common workflow for those wanting to maintain linear histories:
To avoid this, we can move the bulk of the instructions/about/FAQ/etc. in a PR comment, leaving only the core Scala Stweward: update foo bar from v1 to v2 text in the PR description
The text was updated successfully, but these errors were encountered:
@fthomas whether it contains the PR body or not is configurable in repo settings.
In my org, we put a lot more effort into reviewing at PR granularity rather than commit granularity, so the focus is on readable PR descriptions that are then squashed into the single commit description when merging. So we configure the repo to use the PR description as the message. This works great for almost all PRs, except for Scala Steward. And that can be fixed if Scala Steward were tweaked as described in this ticket
Currently, the verbose PR descriptions end up in the commit history by anyone using
Squash and Merge
on Github, which is a relatively common workflow for those wanting to maintain linear histories:To avoid this, we can move the bulk of the instructions/about/FAQ/etc. in a PR comment, leaving only the core
Scala Stweward: update foo bar from v1 to v2
text in the PR descriptionThe text was updated successfully, but these errors were encountered: