docs: fix remaining conductor-sdk org links (csproj + e2e script) - #139
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests.
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
|
Codecov Report✅ All modified and coverable lines are covered by tests.
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
|
Update: reopened and repurposed instead of closing. The README "Next:" link this PR originally fixed was already resolved by the README rewrite on
Left intact: |
The README link this PR originally fixed was already resolved by the README rewrite on main. Update the remaining old-org references that still pointed at conductor-sdk/conductor-csharp: the RepositoryUrl in all five .csproj files and the bundle-README link in scripts/package-e2e-bundle.sh.
Fixes conductor-oss/getting-started#26
The README "Next:" link this PR originally fixed was already resolved by the README rewrite on
main, so that change is now dropped (README is byte-identical to main). Repurposed to clean up the old-org references that still linger elsewhere in the repo:RepositoryUrlin all five.csprojfiles (Conductor,Conductor.AI,Conductor.AI.OpenAI,Conductor.AI.GoogleADK,Conductor.AI.SemanticKernel) →https://github.com/conductor-oss/csharp-sdkscripts/package-e2e-bundle.sh→conductor-oss/csharp-sdkLeft intact:
docs/examples.mdlinks toconductor-sdk/conductor-examples, which is a different repo that has not moved orgs, and the unrelatedUser-Agent = "conductor-sdk"string in an example.User impact: NuGet package pages and the published e2e-test bundle README pointed users at the dead
conductor-sdk/conductor-csharprepo. They now link to the liveconductor-oss/csharp-sdkhome.