Skip to content

Sync eng/common directory with azure-sdk-tools for PR 10523 #40864

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
May 2, 2025

Conversation

azure-sdk
Copy link
Collaborator

Sync eng/common directory with azure-sdk-tools for PR Azure/azure-sdk-tools#10523 See eng/common workflow

@Copilot Copilot AI review requested due to automatic review settings May 2, 2025 15:50
@azure-sdk azure-sdk requested a review from a team as a code owner May 2, 2025 15:50
@azure-sdk azure-sdk requested a review from jorgerangel-msft May 2, 2025 15:50
@azure-sdk azure-sdk added EngSys This issue is impacting the engineering system. Central-EngSys This issue is owned by the Engineering System team. labels May 2, 2025
Copy link
Contributor

@Copilot 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 synchronizes the eng/common directory with the azure-sdk-tools repository to align with their latest pipeline workflows.

  • Inserts a Node.js installation task in the archetype-typespec-emitter pipeline template in two locations.
  • Retains the download pipeline artifacts task following the new Node.js installation step.

@jorgerangel-msft jorgerangel-msft merged commit 0c885b1 into main May 2, 2025
27 checks passed
@jorgerangel-msft jorgerangel-msft deleted the sync-eng/common-bump-emitter-ci-node-10523 branch May 2, 2025 17:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Central-EngSys This issue is owned by the Engineering System team. EngSys This issue is impacting the engineering system.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants