Skip to content
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

Ensure that ScanPaths are always populated in verify-readmes #8998

Merged
merged 1 commit into from
Sep 19, 2024

Conversation

scbedd
Copy link
Member

@scbedd scbedd commented Sep 18, 2024

What happens if a task above the call to verify-readmes fails? Well before this change we would SKIP populating the scan paths, which would then also cause the call to verify readmes to always fail because of no populated ScanPath argument.

This PR matches up the condition to avoid this issue.

…t, and there are previous failures in the analyze pipeline, we won't properly invoke verify readmes.
@scbedd scbedd self-assigned this Sep 18, 2024
@scbedd scbedd requested a review from a team as a code owner September 18, 2024 00:26
@azure-sdk
Copy link
Collaborator

The following pipelines have been queued for testing:
java - template
java - template - tests
js - template
net - template
net - template - tests
python - template
python - template - tests
You can sign off on the approval gate to test the release stage of each pipeline.
See eng/common workflow

scbedd added a commit to Azure/azure-sdk-for-js that referenced this pull request Sep 19, 2024
@scbedd scbedd merged commit d68db39 into Azure:main Sep 19, 2024
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

4 participants