Skip to content

Define and deploy sensible default merge strategy #341

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
Open
1 task
sdruskat opened this issue May 6, 2025 · 0 comments
Open
1 task

Define and deploy sensible default merge strategy #341

sdruskat opened this issue May 6, 2025 · 0 comments
Labels
architecture Describes some architectural decisions that need to be made data model Related to the hermes data model documentation Improvements or additions to documentation meeting-discussion Issues that should be discussed at the next project meeting

Comments

@sdruskat
Copy link
Contributor

sdruskat commented May 6, 2025

Following #153, merging strategies can be very complex, which may impede usability.

  • As per convention over configuration, sensible defaults should be defined, so that for simple cases, users don't have to configure anything. E.g., default is keep precedence, where plugins are run deterministically in the given or default order and no data is ever overwritten by subsequently run plugins.
@sdruskat sdruskat added architecture Describes some architectural decisions that need to be made data model Related to the hermes data model documentation Improvements or additions to documentation enhancement New feature or request meeting-discussion Issues that should be discussed at the next project meeting and removed enhancement New feature or request labels May 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
architecture Describes some architectural decisions that need to be made data model Related to the hermes data model documentation Improvements or additions to documentation meeting-discussion Issues that should be discussed at the next project meeting
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@sdruskat