Disconnect fork #33
Description
This repository is currently connected to the original upstream DataDog repository. This causes difficulties when opening a new pull request that is intended to target the fork; basically, the UI defaults to targeting the original upstream repo without manual intervention and it is very easy to overlook. As an example, nodejs/orchestrion-js#25 was meant to target this forked repo, but I forgot to change the target.
We discussed disconnecting this fork in our cross organization Zoom meeting on 2025-09-03. The decision is that proceeding with asking GitHub to disconnect the fork (https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/detaching-a-fork) is acceptable as long as we continue to prominently advertise this repo is a fork.