[SYSE-394 release-5-lts] Fix test code base for Tyk-Analytics PRs #6582
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
|
API Changes no api changes detected |
buger
force-pushed
the
releng/release-5-lts
branch
3 times, most recently
from
5574af8
to
d3cd222
Compare
💥 CI tests failed 🙈git-stateall okPlease look at the run or in the Checks tab. |
buger
force-pushed
the
releng/release-5-lts
branch
3 times, most recently
from
7885381
to
65a3551
Compare
💥 CI tests failed 🙈git-stateall okPlease look at the run or in the Checks tab. |
buger
force-pushed
the
releng/release-5-lts
branch
4 times, most recently
from
ab797e7
to
7bf06c6
Compare
buger
force-pushed
the
releng/release-5-lts
branch
from
7bf06c6
to
83a6c0c
Compare
|
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.
A PR has been created by to address the PRs on tyk-analytics checking out the wrong base (base branch) when working on a pull-request over the tyk-analytics repo.In this case developers would want to checkout the HEAD of the branch instead of the BASE so they can have their new tests in place for the PR.PR being worked out under QA board: TykTechnologies/gromit#346