You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since all our crates are in a single workspace, it's better that the pipeline commands (scripts, etc.) pass --package (short: -p) when supported because:
It's easier to see what package a command was run on if there's a failure (have to hunt for the directory we pushed into otherwise most times),
It's less maintenance and risk pushing into directories and popping on errors (it's rare, but I've seen the pop fail to be executed).
The text was updated successfully, but these errors were encountered:
Note that, for eng/scripts/Test-Packages.ps1, the package info should already have the package name. If anything, the manifest directory name should match the crate name, though it's best to read the crate name from the manifest if needed.
Since all our crates are in a single workspace, it's better that the pipeline commands (scripts, etc.) pass
--package
(short:-p
) when supported because:The text was updated successfully, but these errors were encountered: