Skip to content

chore(designer): rename 'Foundry Agent Service' to 'Foundry project' in display strings#8794

Merged
ccastrotrejo merged 1 commit intomainfrom
ccastrotrejo/foundry
Feb 5, 2026
Merged

chore(designer): rename 'Foundry Agent Service' to 'Foundry project' in display strings#8794
ccastrotrejo merged 1 commit intomainfrom
ccastrotrejo/foundry

Conversation

@ccastrotrejo
Copy link
Contributor

@ccastrotrejo ccastrotrejo commented Feb 5, 2026

Commit Type

  • feature - New functionality
  • fix - Bug fix
  • refactor - Code restructuring without behavior change
  • perf - Performance improvement
  • docs - Documentation update
  • test - Test-related changes
  • chore - Maintenance/tooling

Risk Level

  • Low - Minor changes, limited scope
  • Medium - Moderate changes, some user impact
  • High - Major changes, significant user/system impact

What & Why

Renames the display string "Foundry Agent Service" to "Foundry project" across the codebase to align with updated product naming conventions.

Impact of Change

  • Users: Users will see "Foundry project" instead of "Foundry Agent Service" in the model type dropdown when configuring agent operations
  • Developers: None - no API changes, only display string updates
  • System: None

Test Plan

  • Unit tests added/updated
  • E2E tests added/updated
  • Manual testing completed
  • Tested in: Unit tests verify the updated constant values

Files Changed

  • libs/designer/src/lib/common/utilities/Utils.ts - Updated AgentUtils.ModelType.FoundryService display value
  • libs/designer-v2/src/lib/common/utilities/Utils.ts - Updated AgentUtils.ModelType.FoundryService display value
  • libs/logic-apps-shared/src/designer-client-services/lib/standard/manifest/agentloop.ts - Updated manifest display name for FoundryAgentService option
  • libs/designer/src/lib/common/utilities/__test__/Utils.test.ts - Updated unit test expectations
  • libs/designer-v2/src/lib/common/utilities/__test__/Utils.test.ts - Updated unit test expectations
  • e2e/designer/real-api/agentic/agentConnections.spec.ts - Updated E2E test to select new display name

Contributors

Screenshots/Videos

Before

CleanShot 2026-02-05 at 11 46 48@2x

After

CleanShot 2026-02-05 at 11 45 25@2x

Copilot AI review requested due to automatic review settings February 5, 2026 16:50
@ccastrotrejo ccastrotrejo added the risk:low Low risk change with minimal impact label Feb 5, 2026
@github-actions
Copy link

github-actions bot commented Feb 5, 2026

🤖 AI PR Validation Report

PR Review Results

Thank you for your submission! Here's detailed feedback on your PR title and body compliance:

PR Title

  • Current: chore(designer): rename 'Foundry Agent Service' to 'Foundry project' in display strings
  • Issue: None — the title is clear, follows conventional commit style (chore scope), and summarizes the change.
  • Recommendation: No change needed.

Commit Type

  • Properly selected (chore).
  • Only one commit type checked, which is correct for this change.

Risk Level

  • The PR body selects Low and the PR has the risk:low label. This matches the code changes.
  • Advised risk based on the diff: Low (small, cosmetic display-string rename across a few files; tests updated accordingly).

What & Why

  • Current: Renames the display string "Foundry Agent Service" to "Foundry project" across the codebase to align with updated product naming conventions.
  • Issue: None — concise and appropriate.
  • Recommendation: No change required.

Impact of Change

  • The Impact section correctly documents user/developer/system impact.
  • Recommendation: Consider adding a note about localization/translation impact if localized strings or downstream documentation need updates (see suggestion below).
    • Users: Users will see "Foundry project" instead of "Foundry Agent Service" in the model type dropdown when configuring agent operations
    • Developers: None - no API changes, only display string updates
    • System: None

Test Plan

  • Unit tests and E2E tests are claimed in the PR body and are present in the code diff (tests updated to expect the new display string). This is correct and sufficient for this change.
  • Recommendation: Ensure CI runs the updated tests and passes before merging.

⚠️ Contributors

  • The Contributors section is blank.
  • Recommendation: If others (PMs, designers, or reviewers) contributed to the idea/review/implementation, please add them to give credit. This is optional and will not block the PR.

Screenshots/Videos

  • Screenshots for Before/After are included.
  • Assessment: Good — visual evidence is provided for the UI change.

Summary Table

Section Status Recommendation
Title No change needed.
Commit Type No change needed.
Risk Level No change needed.
What & Why No change needed.
Impact of Change Consider adding localization note.
Test Plan Ensure CI runs and passes.
Contributors ⚠️ Optionally add contributors if applicable.
Screenshots/Videos No change needed.

Final notes

  • This PR passes the PR title/body checks. The advised risk level is Low, which matches the selected label and the changes in the diff (7 additions / 7 deletions across 6 files: display string updates, unit tests, and one E2E spec).
  • Additional recommendations before merging:
    • Confirm CI passes the updated unit & E2E tests.
    • If your project supports multiple locales, double-check whether localization files or translation teams need to update the corresponding strings (this PR updates display strings in code; translations may still reference the old phrase).
    • Optionally add contributors to the Contributors section to credit reviewers/PMs/designers.

Please update if you want help drafting a short localization note or adding credits to Contributors. Thank you for the clear PR — looks good to merge once CI is green!


Last updated: Thu, 05 Feb 2026 17:00:31 GMT

@ccastrotrejo ccastrotrejo changed the title chore: rename 'Foundry Agent Service' to 'Foundry project' in display… chore: rename 'Foundry Agent Service' to 'Foundry project' in display strings Feb 5, 2026
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR renames the display string "Foundry Agent Service" to "Foundry project" throughout the codebase, reflecting an updated product naming convention. The change is purely cosmetic and affects user-facing display strings without modifying any internal identifiers or logic.

Changes:

  • Updated display name in manifest configuration from "Foundry Agent Service (Preview)" to "Foundry project (Preview)"
  • Updated model type constants in designer utilities from "Foundry Agent Service" to "Foundry project"
  • Updated corresponding unit tests to match new display strings
  • Updated E2E test comment and selector to use new display name

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated no comments.

Show a summary per file
File Description
libs/logic-apps-shared/src/designer-client-services/lib/standard/manifest/agentloop.ts Updated displayName in manifest options for agent model type dropdown
libs/designer/src/lib/common/utilities/Utils.ts Updated ModelType constant for FoundryService display string
libs/designer/src/lib/common/utilities/test/Utils.test.ts Updated test expectation to match new display string
libs/designer-v2/src/lib/common/utilities/Utils.ts Updated ModelType constant for FoundryService display string (v2)
libs/designer-v2/src/lib/common/utilities/test/Utils.test.ts Updated test expectation to match new display string (v2)
e2e/designer/real-api/agentic/agentConnections.spec.ts Updated comment and text selector in E2E test to match new display name

@ccastrotrejo ccastrotrejo changed the title chore: rename 'Foundry Agent Service' to 'Foundry project' in display strings chore(designer): rename 'Foundry Agent Service' to 'Foundry project' in display strings Feb 5, 2026
@github-actions
Copy link

github-actions bot commented Feb 5, 2026

📊 Coverage check completed. See workflow run for details.

@ccastrotrejo ccastrotrejo merged commit 2b2b775 into main Feb 5, 2026
24 of 27 checks passed
@ccastrotrejo ccastrotrejo deleted the ccastrotrejo/foundry branch February 5, 2026 17:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

pr-validated risk:low Low risk change with minimal impact

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants