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
[0] >> git init hubble-otel-test
Initialized empty Git repository in /Users/ilya/Code/otel/hubble-otel-test/.git/
[0] >> cd hubble-otel-test
[0] >> git remote add origin https://github.com/cilium/hubble-otel
[0] >> git config --local gc.auto 0
[0] >> git -c protocol.version=2 fetch --prune --progress --no-recurse-submodules origin '+refs/heads/*:refs/remotes/origin/*' '+refs/tags/*:refs/tags/*'
remote: Enumerating objects: 12347, done.
remote: Counting objects: 100% (12347/12347), done.
remote: Compressing objects: 100% (7815/7815), done.
remote: Total 12347 (delta 4075), reused 11806 (delta 3648), pack-reused 0
Receiving objects: 100% (12347/12347), 20.56 MiB | 8.24 MiB/s, done.
Resolving deltas: 100% (4075/4075), done.
From https://github.com/cilium/hubble-otel
* [new branch] main -> origin/main
* [new branch] user-guides -> origin/user-guides
* [new tag] v0.1.0-rc.1 -> v0.1.0-rc.1
[0] >> git checkout --progress --force refs/tags/v0.1.0-rc.1
Updating files: 100% (6730/6730), done.
Note: switching to 'refs/tags/v0.1.0-rc.1'.
You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by switching back to a branch.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -c with the switch command. Example:
git switch -c <new-branch-name>
Or undo this operation with:
git switch -
Turn off this advice by setting config variable advice.detachedHead to false
HEAD is now at 4a74e1c Do not run tests during image build
This will need to be validated after work on build config is merged into main branch, doesn't make much sense to address it before that as quite a few things are being reworked.
The text was updated successfully, but these errors were encountered: