KEMBAR78
Ensure that the workflows are triggered on `.globalconfig` and other files at the root of the repo by TravisEz13 · Pull Request #26034 · PowerShell/PowerShell · GitHub
Skip to content

Conversation

@TravisEz13
Copy link
Member

@TravisEz13 TravisEz13 commented Sep 10, 2025

PR Summary

This pull request updates the path filters for the CI workflow triggers across all major platforms. The changes ensure that the workflows are triggered on a broader set of file changes, including the addition of the .globalconfig file.

Workflow trigger improvements:

PR Context

#25813 (comment)

PR Checklist

@TravisEz13 TravisEz13 changed the title Add .globalconfig to CI workflow paths Ensure that the workflows are triggered on .globalconfig and other files at the root of the repo Sep 10, 2025
@TravisEz13
Copy link
Member Author

/azp run PowerShell-CI-linux-packaging, PowerShell-Windows-Packaging-CI

@azure-pipelines
Copy link

Azure Pipelines could not run because the pipeline triggers exclude this branch/path.

@TravisEz13 TravisEz13 added the CL-BuildPackaging Indicates that a PR should be marked as a build or packaging change in the Change Log label Sep 10, 2025
@TravisEz13 TravisEz13 marked this pull request as ready for review September 10, 2025 20:25
@TravisEz13 TravisEz13 requested review from a team and jshigetomi as code owners September 10, 2025 20:25
@microsoft-github-policy-service microsoft-github-policy-service bot added the Review - Needed The PR is being reviewed label Sep 18, 2025
@TravisEz13 TravisEz13 merged commit 2d8040f into master Sep 22, 2025
44 of 56 checks passed
@microsoft-github-policy-service
Copy link
Contributor

microsoft-github-policy-service bot commented Sep 22, 2025

📣 Hey @@TravisEz13, how did we do? We would love to hear your feedback with the link below! 🗣️

🔗 https://aka.ms/PSRepoFeedback

@xtqqczze
Copy link
Contributor

What about stylecop.json?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CL-BuildPackaging Indicates that a PR should be marked as a build or packaging change in the Change Log Review - Needed The PR is being reviewed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants