refactoring the Oaf records merge utilities into dhp-common #404

Merged

claudio.atzori merged 4 commits from mergeutils into beta

claudio.atzori commented

Owner

This PR reviews the implementation of the utilities for merging records to provide more fine grained control over the case by case scenarios.

This PR reviews the implementation of the utilities for merging records to provide more fine grained control over the case by case scenarios.

giambattista.bloisi was assigned by claudio.atzori

miriam.baglioni was assigned by claudio.atzori

sandro.labruzzo was assigned by claudio.atzori

claudio.atzori added 1 commit

aaa73f89d1 refactoring the Oaf records merge utilities into dhp-common

claudio.atzori added 1 commit

c8683eb13c Merge branch 'beta' into mergeutils

claudio.atzori added 1 commit

9fc70a9451 implemented default merge procedure applied to result.instance

claudio.atzori added 1 commit

ecff0b4825 merge from beta

claudio.atzori merged commit 414acd4ef4 into beta 1 month ago

claudio.atzori referenced this issue from a commit

Merge pull request 'refactoring the Oaf records merge utilities into dhp-common' (#404) from mergeutils into beta

giambattista.bloisi referenced this issue from a commit

Refinements to PR #404: refactoring the Oaf records merge utilities into dhp-common

giambattista.bloisi referenced this pull request

Refinements to PR #404: refactoring the Oaf records merge utilities into dhp-common #422

claudio.atzori referenced this issue from a commit

Merge pull request 'Refinements to PR #404: refactoring the Oaf records merge utilities into dhp-common' (#422) from revised_merge_logic into beta

The pull request has been merged as 414acd4ef4.

You can also view command line instructions.

Step 1:

From your project repository, check out a new branch and test the changes.

git checkout -b mergeutils beta

git pull origin mergeutils

Step 2:

Merge the changes and update on Gitea.

git checkout beta

git merge --no-ff mergeutils

git push origin beta

Sign in to join this conversation.

No reviewers

No Label

No Milestone

No project

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Loading…

There is no content yet.