What are the steps for rebasing an issue fork of core to the latest code plus 'patch'?

cn flag

It appears the current version of Drupal outside the issue fork needs to be added as a remote repository, but i'm getting tripped up on creating it as a branch i can rebase against.

Hoping the answer to this is a link to documentation, but does not mention the issue fork workflow.

cn flag

This seems to do it, where '3029545' is the issue number which is forked, these steps are presumed to have happened first:

git clone [email protected]:issue/drupal-3029545.git
cd drupal-3029545

And now rebasing on most recent Drupal core:

git checkout 3029545-add-route-exists # check out the branch in development
git remote add drupal [email protected]:project/drupal.git
git fetch drupal
git rebase drupal/9.2.x # current core branch

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.