![]() For example, let's say a developer has started working on a new feature. When a bug is discovered, it is essential to fix that quickly as possible. This selection would allow the developer of the front end to continue progress on their project side. In order to select the commit in which this hypothetical data structure was created, the frontend developer could use git cherry-pick. Perhaps the developer of the backend produces a data structure that will also need to be used by the frontend. There may be some shared code between two sectors of the product. Perhaps there is a backend and frontend component of a new product feature. CollaborationĪ team will often find individual members working in or around the same code sometimes. Git cherry-pick is a useful option for a few situations. Cherry-picking can trigger duplicate commits, and traditional merges are preferred instead in many situations where cherry-picking would work. Git cherry-pick is a useful tool but isn't best practice always. ![]() The neutron commit has been successfully picked into the feature branch. Once executed, our Git history will look like: alpha - beta - gama - delta - neutron `Master` \ x - neutron - Ultraviolet `Feature` We make sure that we are working on the master branch first.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |