chore: clean up after circleci removal
galargh committed
Mar 2, 2023 at 09:11 UTC
ceed43ea0e4b402f8873f4bfe47ee8a191e99a5f
5 files changed
+8
-18
README.md
+2
-3
@@ -3,7 +3,6 @@
3
4
[](https://protocol.ai)
5
[](https://godoc.org/github.com/ipfs/kubo)
6
-[](https://circleci.com/gh/ipfs/kubo)
6
7
## What is Kubo?
8
@@ -33,7 +32,7 @@ Before opening an issue, consider using one of the following locations to ensure
32
- Exploration of new ideas in [ipfs/notes issues](https://github.com/ipfs/notes/issues).
33
- Ask questions and meet the rest of the community at the [IPFS Forum](https://discuss.ipfs.tech).
34
- Or [chat with us](https://docs.ipfs.tech/community/chat/).
36
-
35
+
36
[](https://www.youtube.com/channel/UCdjsUXJ3QawK4O5L1kqqsew) [](https://twitter.com/IPFS)
37
38
## Next milestones
@@ -68,7 +67,7 @@ Before opening an issue, consider using one of the following locations to ensure
67
- [Unofficial MacOS packages](#unofficial-macos-packages)
68
- [MacPorts](#macports)
69
- [Nix](#nix-macos)
71
- - [Homebrew](#homebrew)
70
+ - [Homebrew](#homebrew)
71
- [Build from Source](#build-from-source)
72
- [Install Go](#install-go)
73
- [Download and Compile IPFS](#download-and-compile-ipfs)
bin/get-docker-tags.sh
+1
-4
@@ -6,16 +6,13 @@
6
# ./get-docker-tags.sh <build number> <git commit sha1> <git branch name> [git tag name]
7
#
8
# Example:
9
-#
9
+#
10
# # get tag for the master branch
11
# ./get-docker-tags.sh $(date -u +%F) testingsha master
12
#
13
# # get tag for a release tag
14
# ./get-docker-tags.sh $(date -u +%F) testingsha release v0.5.0
15
#
16
-# # Serving suggestion in circle ci - https://circleci.com/docs/2.0/env-vars/#built-in-environment-variables
17
-# ./get-docker-tags.sh $(date -u +%F) "$CIRCLE_SHA1" "$CIRCLE_BRANCH" "$CIRCLE_TAG"
18
-#
16
set -euo pipefail
17
18
if [[ $# -lt 1 ]] ; then
bin/mkreleaselog
-1
@@ -41,7 +41,6 @@ IGNORE_FILES=(
41
"go.mod"
42
"go.sum"
43
".github"
44
- ".circleci"
44
"*.pb.go"
45
"cbor_gen.go"
46
"ipldsch_*.go"
bin/push-docker-tags.sh
+4
-8
@@ -2,11 +2,10 @@
2
3
# push-docker-tags.sh
4
#
5
-# Run from ci to tag images based on the current branch or tag name.
5
+# Run from ci to tag images based on the current branch or tag name.
6
# A bit like dockerhub autobuild config, but somewhere we can version control it.
7
-#
8
-# The `docker-build` job in .circleci/config.yml builds the current commit
9
-# in docker and tags it as ipfs/go-ipfs:wip
7
+#
8
+# The `docker-build` job builds the current commit in docker and tags it as ipfs/go-ipfs:wip
9
#
10
# Then the `docker-publish` job runs this script to decide what tag, if any,
11
# to publish to dockerhub.
@@ -17,16 +16,13 @@
16
# Example:
17
# # dry run. pass a 5th arg to have it print what it would do rather than do it.
18
# ./push-docker-tags.sh $(date -u +%F) testingsha master "" dryrun
20
-#
19
+#
20
# # push tag for the master branch
21
# ./push-docker-tags.sh $(date -u +%F) testingsha master
22
#
23
# # push tag for a release tag
24
# ./push-docker-tags.sh $(date -u +%F) testingsha release v0.5.0
25
#
27
-# # Serving suggestion in circle ci - https://circleci.com/docs/2.0/env-vars/#built-in-environment-variables
28
-# ./push-docker-tags.sh $(date -u +%F) "$CIRCLE_SHA1" "$CIRCLE_BRANCH" "$CIRCLE_TAG"
29
-#
26
set -euo pipefail
27
28
if [[ $# -lt 1 ]] ; then
codecov.yml
+1
-2
@@ -1,10 +1,9 @@
1
codecov:
2
ci:
3
- - "ci/circle-ci"
3
- "!travis-ci.org"
4
- "!ci.ipfs.team:8111"
5
- "!ci.ipfs.team"
7
- - "!github.com"
6
+ - "github.com"
7
notify:
8
require_ci_to_pass: no
9
after_n_builds: 2