Git history overwritten when providing link to different repository

[ben-laird]

Context & Background

I wanted to try using Changesets for a personal project of mine, a Deno monorepo. I used the JavaScript API/package provided so that I could programmatically run checks or builds before cutting a release. Because my project was entirely local, during my testing I provided a URL to a different GitHub repository. I later found out that my Git history for the topic branch I was working in and my main branch were overwritten with the history of this other repository.

Expected Behavior

Changesets should only read commits when generating changelogs and analyzing commit messages, and it should not overwrite any local Git history.

---

Apologies if this isn't much information to go on. If you have any questions, I'd love to answer them and help get to the bottom of this. I'd love to use changesets more often in my projects, but a situation like this really scares me away from using the tool.

[Andarist]

What workflow (what executed commands etc) led to this?

[ben-laird]

I'm so sorry, I think I filed this issue in the wrong repository. I think I was using the Semantic Release JavaScript API which gives programmatic access to the Semantic Release tool. Obviously, this is the wrong repository to be filing issues for Semantic Release. Apologies again! I'll mark this issue as closed. Thanks so much for getting back to me!