This repository has been archived by the owner on Jan 4, 2023. It is now read-only.
fix: correctly output junit report in target repository #32
Conversation
This file contains 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
dhayab
requested review from
a team,
francoischalifour and
Haroenv
and removed request for
a team
Haroenv
approved these changes
Jan 18, 2022
francoischalifour
approved these changes
Jan 18, 2022
Haroenv
pushed a commit
to algolia/instantsearch
that referenced
this pull request
Nov 24, 2022
Haroenv
pushed a commit
to algolia/instantsearch
that referenced
this pull request
Nov 24, 2022
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
A previous PR added automatic JUnit report generation for tested projects. Unfortunately, those reports were generated in node_modules/instantsearch-e2e-tests instead of the root of the tested repositories.
This PR fixes that.