Buradasın
GitLab Cherry-pick Features
docs.gitlab.com/user/project/merge_requests/cherry_pick_changes/Yapay zekadan makale özeti
- What is Cherry-picking
- Cherry-picking adds single commits from one branch to another
- Only selected commits from source branch are added to target
- Useful for backporting bug fixes and copying changes between repositories
- Prerequisites and Requirements
- Requires merge request editing role and Merge Commit merge method
- Fast-forwarded commits can be cherry-picked only when squashed
- Available in Free, Premium, and Ultimate tiers
- UI Cherry-picking Methods
- Can cherry-pick from project's commit list
- Available from file view in repository history
- System notes added for cherry-picked commits
- Additional Features
- Can cherry-pick changes from merge requests
- Mainline is always first parent in UI cherry-picking
- Commits outside UI don't add system notes