This repository has been archived by the owner on Jun 28, 2024. It is now read-only.
[stable-2.1] Refer to stable-2.1 branch instead of main, for content that's part of stable-2.1 branch
#3507
Comments
fidencio
added
bug
fidencio
added a commit
to fidencio/kata-tests
that referenced
this issue
May 7, 2021
This commit forces all the checks and references to point to stable-2.1 branch rather than pointing to `main`. This will guarantee that changes done on `main` won't affect the testing of this specific branch. Fixes: kata-containers#3507 Signed-off-by: Fabiano Fidêncio <[email protected]>
fidencio
added a commit
to fidencio/kata-tests
that referenced
this issue
May 10, 2021
This commit forces all the checks and references to point to stable-2.1 branch rather than pointing to `main`. This will guarantee that changes done on `main` won't affect the testing of this specific branch. Fixes: kata-containers#3507 Signed-off-by: Fabiano Fidêncio <[email protected]>
fidencio
added a commit
to fidencio/kata-tests
that referenced
this issue
May 11, 2021
This commit forces all the checks and references to point to stable-2.1 branch rather than pointing to `main`. This will guarantee that changes done on `main` won't affect the testing of this specific branch. Fixes: kata-containers#3507 Signed-off-by: Fabiano Fidêncio <[email protected]>
fidencio
added
area/ci
and removed
needs-review
|
Closed by #3504 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It's not uncommon that we'll update content on main and our branches will not be updated accordingly. This is, actually, kind of expected.
In order to avoid broken links, broken references, or even mistakenly testing against a different repo, let's ensure we point our references to
stable-2.1onstable-2.1branch.The text was updated successfully, but these errors were encountered: