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
After I forked a repo and made several commits, I found that this issue should not be fixed first, but rather another issue.
Then I want to resynchronize the upstream repo. But Github told me:
Then I must enter the setting, delete this warehouse, and fork again. Otherwise, you need to use the command line to resynchronize upstream.
✨I hope there can be a forced synchronization upstream operation here, regardless of the situation, as long as the code of the branch is inconsistent (whether it is here or adding a function to the fork code in the setting,Even if a second password verification is required)
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Select Topic Area
Question
Body
After I forked a repo and made several commits, I found that this issue should not be fixed first, but rather another issue.
Then I want to resynchronize the upstream repo. But Github told me:
Then I must enter the setting, delete this warehouse, and fork again. Otherwise, you need to use the command line to resynchronize upstream.
✨I hope there can be a forced synchronization upstream operation here, regardless of the situation, as long as the code of the branch is inconsistent (whether it is here or adding a function to the fork code in the setting,Even if a second password verification is required)
Beta Was this translation helpful? Give feedback.
All reactions