-
Notifications
You must be signed in to change notification settings - Fork 539
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
chore: simplify e2e env #2694
Merged
Merged
chore: simplify e2e env #2694
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
Codecov Report
@@ Coverage Diff @@
## master #2694 +/- ##
==========================================
- Coverage 76.34% 66.96% -9.38%
==========================================
Files 139 198 +59
Lines 3754 7750 +3996
Branches 874 870 -4
==========================================
+ Hits 2866 5190 +2324
- Misses 888 2258 +1370
- Partials 0 302 +302
Flags with carried forward coverage won't be shown. Click here to find out more.
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
bzp2010
force-pushed
the
chore-simplify-e2e-env
branch
3 times, most recently
from
December 16, 2022 09:34
b50dab0
to
102d9f0
Compare
bzp2010
force-pushed
the
chore-simplify-e2e-env
branch
from
December 16, 2022 09:44
102d9f0
to
ebfb0ec
Compare
bzp2010
force-pushed
the
chore-simplify-e2e-env
branch
from
December 16, 2022 10:04
0377f41
to
acbcd32
Compare
bzp2010
force-pushed
the
chore-simplify-e2e-env
branch
2 times, most recently
from
December 20, 2022 05:39
0a3d9cb
to
a09a960
Compare
bzp2010
force-pushed
the
chore-simplify-e2e-env
branch
from
December 20, 2022 08:04
a09a960
to
f41a393
Compare
bzp2010
force-pushed
the
chore-simplify-e2e-env
branch
from
December 21, 2022 03:43
bb51f3f
to
ba54ae2
Compare
juzhiyuan
approved these changes
Dec 21, 2022
guoqqqi
approved these changes
Dec 21, 2022
hongbinhsu
added a commit
to fitphp/apix-dashboard
that referenced
this pull request
Jan 30, 2023
* upstream/master: feat: release 3.0.0 (apache#2722) Revert "feat: release 2.16.0 (apache#2719)" (apache#2721) feat: release 2.16.0 (apache#2719) fix: plugin configuration lost in editor (apache#2718) fix: adapt APISIX plugin disabled (apache#2717) feat: basic support Apache APISIX 3.0.0 (apache#2701) feat: change etcd prefix for ssl and proto (apache#2693) fix: remove cases external service dependency (apache#2697) chore: simplify e2e environment (apache#2694) chore: optimize "allow_origins_by_regex tooltip" description (apache#2690) feat: release 2.15.0 (apache#2685) feat: basic support Apache APISIX 2.15.0 (apache#2680) feat: release 2.14.0 (apache#2677) fix: bump go version to 1.16 (apache#2678) feat: release 2.13.1 (apache#2658) feat: support more upstream scheme (apache#2675) feat: support purge method (apache#2674) feat: add enable flag to oidc function (apache#2672) # Conflicts: # web/package.json
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.
Please answer these questions before submitting a pull request, or your PR will get closed.
Why submit this pull request?
What changes will this PR take into?
Simplify the E2E testing environment and reduce the mental burden.
Checklist: