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
It has been suggested on the Python Core Devs Discord that we should enable the newish GitHub repo option to always suggest updating pull request branches when they are out-of-date when the current branch head. That would simplify the PR contribution experience in the not infrequent case when a PR CI job fails due to some unrelated change that has been subsequently fixed. As an experiment, I've already enabled it for cpython after some discussion on Discord and it does seem to be useful. If we want to make that a permanent change, we should announce it to the developer community and add something to the devguide.
The text was updated successfully, but these errors were encountered:
@brettcannon Beat you to what ? :) I changed the setting on the repo before opening the issue. I opened the issue to make sure we had consensus that it was the right thing to do and then, if so, announce it and document it in the devguide. Or do you think that none of that is necessary?
Ah, I thought you were asking me to flip it. The setting is flipping on an unobtrusive feature and I thought it was discussed enough on Discord, so I wasn't worried about more discussion.
It has been suggested on the Python Core Devs Discord that we should enable the newish GitHub repo option to always suggest updating pull request branches when they are out-of-date when the current branch head. That would simplify the PR contribution experience in the not infrequent case when a PR CI job fails due to some unrelated change that has been subsequently fixed. As an experiment, I've already enabled it for cpython after some discussion on Discord and it does seem to be useful. If we want to make that a permanent change, we should announce it to the developer community and add something to the devguide.
The text was updated successfully, but these errors were encountered: