You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Attempting to fix the state of codecov action checks right now,
which are behaving very erratically.
Using the new functionality in Go 1.20 to merge multiple reports,
so now the unit & E2E coverage data reports are stored as artifacts
and then downloaded, merged, and finally uploaded to codecov as a
new job.
Additionally, add a `codecov.yml` config and try to turn down the
aggressiveness of it for CI checks.
Signed-off-by: Milas Bowman <[email protected]>
# DESTDIR overrides the output path for binaries and other artifacts
43
+
# this is used by docker/docker-ce-packaging for the apt/rpm builds,
44
+
# so it's important that the resulting binary ends up EXACTLY at the
45
+
# path $DESTDIR/docker-compose when specified.
46
+
#
47
+
# See https://github.com/docker/docker-ce-packaging/blob/e43fbd37e48fde49d907b9195f23b13537521b94/rpm/SPECS/docker-compose-plugin.spec#L47
48
+
#
49
+
# By default, all artifacts go to subdirectories under ./bin/ in the
50
+
# repo root, e.g. ./bin/build, ./bin/coverage, ./bin/release.
0 commit comments