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
If people have PRs that start out against 2018 and switched to be pulled into dev, they will include the merge commits from dev to 2018, which looks odd.
We should make it part of our procedure to merge 2018 back into dev so the merge from dev to 2018 is included in master.
I don't know another way to do this without asking people to rebase their branches onto dev.
So we should update the instructions to reflect that.
The text was updated successfully, but these errors were encountered:
If people have PRs that start out against 2018 and switched to be pulled into dev, they will include the merge commits from dev to 2018, which looks odd.
We should make it part of our procedure to merge 2018 back into dev so the merge from dev to 2018 is included in master.
I don't know another way to do this without asking people to rebase their branches onto dev.
So we should update the instructions to reflect that.
The text was updated successfully, but these errors were encountered: