-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Further net - pullrequest
tuning
#48379
Conversation
…ests to be always included even when it shouldn't be.
…aths on artifactDetails
…e that we don't attempt to build the .net integration tests when packing
@weshaggard ok I think this is ready to go in. There is another cleanup commit I could do re: removing the triggering paths for template, but honestly I don't want to add another commit to this PR. There will be one last follow-up where I figure out what I want to do with service-level changes to directories with multiple |
/check-enforcer override The snippets issue in |
This PR:
isOther
function inlanguage-settings
as the built-in functionality inGet-PrPkgProperties
now resolves for Shared packages if the necessary metadata is present.*.Shared
-named package is present" in favor of a explicit usage oftriggeringPaths
. Now if Azure.Messaging.EventHubs.Shared is changed, we will indirectly run tests forAzure.Messaging.EventHubs
andAzure.Messaging.EventHubs.Processor
, but NONE of the other track1 / functions packages. @jsquire FYIIntegrationTests
a class of package that can be directly excluded from property. Excludeintegration
test packages frompack
for PRs.todo:
Shared
packages like foreventhub
to ensure their triggeringPaths are configured properly.Microsoft.
packages when we've explicitly updated the language-settings to not cause that anymore.ci.yml
files must only apply to the artifacts within. (this is why the microsoft eventhub namespaces are being added rn)