Closed Magador closed 9 months ago
Name | Link |
---|---|
Latest commit | acffcc1616b896463d226385f9d7f6e756cc88ec |
Latest deploy log | https://app.netlify.com/sites/xenodochial-hugle-b9ec84/deploys/657c9f925cf72c0008088eba |
Deploy Preview | https://deploy-preview-1120--xenodochial-hugle-b9ec84.netlify.app/ |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
Wow @Magador I really appreciate the contribution! You wrote tests and explained the small change in the git engine and thought about everything 🙌🏻
I'm not super familiar with these alternate workflows for merging features (at Instagram we all just merge into one main trunk branch) but sounds like you've thought about these a lot. I'll merge and push the site now with the updates 😎
Yeah :)
thanks @Magador
that's good ! Where can i do this experiment ? I do not find this one in https://learngitbranching.js.org/?locale=zh_CN
that's good ! Where can i do this experiment ? I do not find this one in https://learngitbranching.js.org/?locale=zh_CN
You can simulate a merge using the sandbox and creating a remote repo :
git clone;
git switch -c feat;
git commit;
git push;
git fakeTeamwork;
git mergeMR feat main;
yes, it works
git merge(M|P)R <source_branch> <target_branch> [--delete-after-merge]
command to simulate a Merge/Pull Request being merged into the target branch--delete-after-merge
will remove the merged branch on the origin treegit fetch
(it would requiregit fetch --prune
support to automatically prune remote tracking branches)Resolves #1057
Examples
Merging a feature branch
feat
intomain
onorigin
Merging a feature branch
feat
intomain
onorigin
when deleting it after mergingIf you
git fetch
after usinggit mergeMR
, the refo/feat
will still exist becausegit fetch
does not prune it by default:You can re-push the local branch, re-creating a remote branch, and updating the ref
o/feat
: