Merge branch 'main' into reuse

Signed-off-by: Charles-Edouard Brétéché <charles.edouard@nirmata.com>
kyverno · Oct 28, 2023 · 813ff87 · 813ff87
2 parents e7de663 + fad714d
commit 813ff87
Show file tree

Hide file tree

Showing 4 changed files with 3 additions and 10 deletions.
diff --git a/docs/dev/labels/README.md → .docs/LABELS.md b/docs/dev/labels/README.md → .docs/LABELS.md
diff --git a/docs/dev/release/README.md → .docs/README.md b/docs/dev/release/README.md → .docs/README.md
@@ -6,7 +6,7 @@ This docs contains informations for releasing releasing.
 
 Creating a release can be done by pushing a tag to the GitHub repository (begining with `v`).
 
-The [release workflow](../../.github/workflows/release.yaml) will take care of creating the GitHub release and will publish artifacts.
+The [release workflow](../.github/workflows/release.yaml) will take care of creating the GitHub release and will publish artifacts.
 
 ```shell
 VERSION="v0.1.0"
@@ -18,8 +18,8 @@ git push origin $TAG
 
 ## Release notes
 
-Release notes for the `main` branch lives in [main.md](../../.release-notes/main.md).
+Release notes for the `main` branch lives in [main.md](../.release-notes/main.md).
 
 Make sure it is up to date and rename the file to the version being released.
 
-You can then copy [_template.md](../../.release-notes/_template.md) to [main.md](../../.release-notes/main.md) for the next release.
+You can then copy [_template.md](../.release-notes/_template.md) to [main.md](../.release-notes/main.md) for the next release.
diff --git a/docs/README.md b/docs/README.md
@@ -2,5 +2,4 @@
 
 This documentation contains the following docs:
 
-- [Dev docs](./dev/README.md)
 - [User docs](./user/README.md)
diff --git a/docs/dev/README.md b/docs/dev/README.md