Dmitri Bourlatchkov

> Should the merge set the created at to the merge timestamp? I'd think the "created" timestamp should be a `min("created" on merge source branch, "created" on target branch)`.

> If these new attributes get included in the events API one day, [...] I'm not sure these new attributes are useful in events. The "created" timestamp looks like a...

Not a duplication IMO... #6447 is about having the "no common ancestor" error in principle. I think the plan is to resolve that with the `allow-unrelated-histories` (new) merge option. This...

Thanks for bringing this matter up, @mthirani2021 ! The error is technically correct, because `dev` was created when `main` did not have any commits, so the two branches, indeed, do...

For reference: `git` does not allow merging unrelated branches by default... e.g. ``` $ git merge dev1 fatal: refusing to merge unrelated histories ```

Re: "related" - please check the Nessie commit log. Branches are "related" only when they have at least one common commit in their respective commit logs.

I propose adding an option similar to git's `--allow-unrelated-histories` to the merge parameters in REST API v2.

@SanjayVas : Thanks for the detailed analysis! We'll see what can be done. Still, if you have a particular fix in mind please feel free to open a PR.

ATM, Nessie [has Iceberg REST API](https://github.com/projectnessie/nessie/pull/7043) on `main`, but it's not released yet.

It might be best to talk about Nessie releases in the project's Zulip chat (the join link is on projectnessie.org) :)