Add OddDotNet registry files

[DoubleTK]

I'm requesting to add OddDotNet and the CSharp client to the registry.

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: DoubleTK / name: Tyler Kenna (84d52f7, 47f079f, 674ccd1, 5645d1d, 4775e25, 5a145cc, 0efb4c1, 8312828, 5ac41aa, 220dc6b, 4743743, a5e5a6f)

[cartermp]

/fix:all

[opentelemetrybot]

You triggered fix:all action run at https://github.com/open-telemetry/opentelemetry.io/actions/runs/11766713320

[opentelemetrybot]

fix:all failed or was cancelled. For details, see https://github.com/open-telemetry/opentelemetry.io/actions/runs/11766713320.

[DoubleTK]

/fix:htmltest-config

[opentelemetrybot]

You triggered fix:htmltest-config action run at https://github.com/open-telemetry/opentelemetry.io/actions/runs/11771629503

[opentelemetrybot]

fix:htmltest-config was successful.

IMPORTANT: (RE-)RUN /fix:all to ensure that there are no remaining check issues.

[DoubleTK]

/fix:all

[opentelemetrybot]

You triggered fix:all action run at https://github.com/open-telemetry/opentelemetry.io/actions/runs/11771653347

[opentelemetrybot]

fix:all failed or was cancelled. For details, see https://github.com/open-telemetry/opentelemetry.io/actions/runs/11771653347.

[svrnm]

@DoubleTK do not worry about the CI checks failing, we can help you with that for merging the PR

[svrnm]

a few more comments

[svrnm]

/fix:htmltest-config

[opentelemetrybot]

You triggered fix:htmltest-config action run at https://github.com/open-telemetry/opentelemetry.io/actions/runs/11818285987

[opentelemetrybot]

fix:htmltest-config was successful.

IMPORTANT: (RE-)RUN /fix:all to ensure that there are no remaining check issues.

[svrnm]

@DoubleTK can you update the PR to be in sync with the base branch?

Note: Creating PRs from an ORG account like https://github.com/OddDotNet/ does not allow maintainers to edit your PR, so a lot of our automation does not work. Therefor for future PRs I recommend you fork from your user handle (DoubleTK) and push your PRs from there.

[DoubleTK]

@DoubleTK can you update the PR to be in sync with the base branch?

Note: Creating PRs from an ORG account like https://github.com/OddDotNet/ does not allow maintainers to edit your PR, so a lot of our automation does not work. Therefor for future PRs I recommend you fork from your user handle (DoubleTK) and push your PRs from there.

Ah, that's good to know, I wasn't aware of that limitation. Thank you for the info, I'll make sure to do that next time. Updating branch with latest main now.

[svrnm]

@DoubleTK can you run npm run fix:all locally and update the changes?

[DoubleTK]

@DoubleTK can you run npm run fix:all locally and update the changes?

I did this, and it ran mostly successfully except for the git submodule update step: "fatal: destination path '/Users/tylerkenna/Projects/opentelemetry.io/content-modules/opentelemetry-go' already exists and is not an empty directory."

Despite running the fix:all command, there were no changes detected, so nothing to push.

Would it be easier for me to abandon this PR and re-open under my personal account? In the meantime, I'll try to run that failing "BUILD and CHECK LINKS" step again here and see if that resolves it.

[DoubleTK]

/fix:htmltest-config

[opentelemetrybot]

You triggered fix:htmltest-config action run at https://github.com/open-telemetry/opentelemetry.io/actions/runs/11843149359

[opentelemetrybot]

fix:htmltest-config was successful.

IMPORTANT: (RE-)RUN /fix:all to ensure that there are no remaining check issues.

[svrnm]

@DoubleTK the issue is that you need to have your URLs added to the refcache. Since we can not edit this PR for you, there are 2 options:

• run npm run fix:refcache locally and commit the changes
• make this PR editable, following these instructions or re-raise the PR using a non-org handle

[DoubleTK]

@DoubleTK the issue is that you need to have your URLs added to the refcache. Since we can not edit this PR for you, there are 2 options:

• run npm run fix:refcache locally and commit the changes
• make this PR editable, following these instructions or re-raise the PR using a non-org handle

I think I'm going to take that second option and redo this using my personal account rather than org. I'll get that PR created first, and then paste the link here and abandon this PR.

[DoubleTK]

Okay I've created a new PR using my personal to allow for maintainer edits. Here's the link:

#5617.

Thank you again for your help and patience, I appreciate it.