Update path in fetch request for known issues file.#243
Merged
alejandro5042 merged 1 commit intoalejandro5042:masterfrom Apr 17, 2026
Merged
Update path in fetch request for known issues file.#243alejandro5042 merged 1 commit intoalejandro5042:masterfrom
alejandro5042 merged 1 commit intoalejandro5042:masterfrom
Conversation
The pipeline-results folder was renamed to pipeline_results in PR !1071498. The file path in known-issues.json needs to be updated to reflect this change.
|
Thanks for opening this pull request! Please check out our contributing guidelines. |
Owner
|
@sbagchini - Do you still want this change? I'll approve if you still want it and it still works today! Sorry for the delay. |
alejandro5042
approved these changes
Apr 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem: The
pipeline-resultsfolder was renamed topipeline_resultsin PR !1071498, but the fetch request path in the known issues functionality was not updated accordingly causing the "Known Errors" to not show up.Solution: Updated the
known-issues.jsonfile path in the fetch request to use the newpipeline_resultsdirectory name.Changes
Testing