Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Per-Object Merge Strategy #3639

Open
itaiad200 opened this issue Jul 10, 2022 · 1 comment
Open

Per-Object Merge Strategy #3639

itaiad200 opened this issue Jul 10, 2022 · 1 comment
Labels
no stale Using this label will prevent items from being marked as stale team/versioning-engine Team versioning engine

Comments

@itaiad200
Copy link
Contributor

The current merge strategies enables to choose the source or destination branch for all conflicted objects. It's better if we'll have a per-object option since not all object always require the same conflict behaviour.
@itaiad200 itaiad200 added the team/versioning-engine Team versioning engine label Jul 10, 2022
@Jonathan-Rosenberg Jonathan-Rosenberg mentioned this issue Oct 4, 2022
Merged
@arielshaqed arielshaqed mentioned this issue Oct 23, 2023
Merged
@github-actions GitHub Actions
Copy link

github-actions bot commented Nov 1, 2023

This issue is now marked as stale after 90 days of inactivity, and will be closed soon. To keep it, mark it with the "no stale" label.

@github-actions github-actions bot added the stale label Nov 1, 2023
@itaiad200 itaiad200 added no stale Using this label will prevent items from being marked as stale and removed stale labels Nov 2, 2023
@github-actions github-actions bot added the stale label Mar 20, 2024
@arielshaqed arielshaqed removed the stale label Mar 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
no stale Using this label will prevent items from being marked as stale team/versioning-engine Team versioning engine
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@arielshaqed @itaiad200