chore(test): remove now-redundant self-repo-bleed workaround overrides - #6536
Merged
Merged
Conversation
#6493 fixed the root cause (createTestEnv()'s default no longer matches any real fixture repo name), making the earlier per-test LOOPOVER_DRIFT_ISSUE_REPO: "unrelated-org/unrelated-repo" workaround in these two files redundant.
Contributor
|
Superagent didn't find any vulnerabilities or security issues in this PR. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #6536 +/- ##
=======================================
Coverage 95.56% 95.56%
=======================================
Files 589 589
Lines 47121 47121
Branches 14989 14989
=======================================
Hits 45032 45032
Misses 1297 1297
Partials 792 792
Flags with carried forward coverage won't be shown. Click here to find out more. |
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
1 participant
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.
Summary
#6493 fixed the root cause of the self-repo manifest bleed (`createTestEnv()`'s default no longer matches any real fixture repo name), which made the earlier per-test `LOOPOVER_DRIFT_ISSUE_REPO: "unrelated-org/unrelated-repo"` workaround in `test/unit/outcomes-wire.test.ts` and `test/unit/rag-index.test.ts` redundant. These two files aren't part of the Batch A config-as-code migration, just carried the same now-obsolete workaround from an earlier fix.
Scope
Validation