Breaking other folder into smaller subfolders

Related Issue(s)
Closes #688

Description
Made subfolders based on first names of the folders inside other. Those with the similar first name were moved to a new folder, rest were left as they were.  For example, restrict-service-port-name and restrict-wildcard-resources were moved inside the folder named restrict.
Test time was reduced from 13 min to around 4 minutes.
Before:

After:

Checklist

[x] I have read the policy contribution guidelines.
[] I have added test manifests and resources covering both positive and negative tests that prove this policy works as intended.
[] I have added the artifacthub-pkg.yml file and have verified it is complete and correct.

Thanks for this PR, @prady0t. Appreciate you taking it on. While this grouping does work, I personally think it's a bit awkward. What I think is a bit more standard and maybe is easier to understand is if we go with an alphabetical range approach. For example, have subfolders with the name a-d, e-i, j-n, etc. We would want to try and find the best divider so that we parcel them up into, more or less, equivalent sizes so that one folder doesn't have 50 policies inside and another has 5. Things like that.
Can you take a look at this from that angle and see what you come up with?

Ah yes I thought about it! Maybe I should have discussed that idea. I did sort folders exactly equal which brought down timing to be under 2 min. nvm doing the changes now👍🏻

That sounds good. Commit them and see what happens. Also be mindful you have conflicting files in this PR which must be resolved.

Pull in all changes from main and you should see the conflicts in your git diff.

@chipzoller in my terminal it shows all conflicts are regarding changed file locations
❯ git merge origin/main
CONFLICT (file location): other/record-creation-details/01-policy.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/record-creation-details/01-policy.yaml.
CONFLICT (file location): other/record-creation-details/02-manifests.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/record-creation-details/02-manifests.yaml.
CONFLICT (file location): other/record-creation-details/03-update.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/record-creation-details/03-update.yaml.
CONFLICT (file location): other/record-creation-details/ns-patched.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/record-creation-details/ns-patched.yaml.
CONFLICT (file location): other/record-creation-details/ns.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/record-creation-details/ns.yaml.
CONFLICT (file location): other/record-creation-details/pod-patch01.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/record-creation-details/pod-patch01.yaml.
CONFLICT (file location): other/record-creation-details/pod-patch02.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/record-creation-details/pod-patch02.yaml.
CONFLICT (file location): other/record-creation-details/pod-patched.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/record-creation-details/pod-patched.yaml.
CONFLICT (file location): other/record-creation-details/pod.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/record-creation-details/pod.yaml.
CONFLICT (file location): other/record-creation-details/policy-ready.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/record-creation-details/policy-ready.yaml.
CONFLICT (file location): other/refresh-env-var-in-pod/00-crb.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/refresh-env-var-in-pod/00-crb.yaml.
CONFLICT (file location): other/refresh-env-var-in-pod/01-policy.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/refresh-env-var-in-pod/01-policy.yaml.
CONFLICT (file location): other/refresh-env-var-in-pod/02-manifests.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/refresh-env-var-in-pod/02-manifests.yaml.
CONFLICT (file location): other/refresh-env-var-in-pod/03-store-deploy-name.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/refresh-env-var-in-pod/03-store-deploy-name.yaml.
CONFLICT (file location): other/refresh-env-var-in-pod/04-secret.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/refresh-env-var-in-pod/04-secret.yaml.
CONFLICT (file location): other/refresh-env-var-in-pod/05-check.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/refresh-env-var-in-pod/05-check.yaml.
CONFLICT (file location): other/refresh-env-var-in-pod/deployment.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/refresh-env-var-in-pod/deployment.yaml.
CONFLICT (file location): other/refresh-env-var-in-pod/ns.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/refresh-env-var-in-pod/ns.yaml.
CONFLICT (file location): other/refresh-env-var-in-pod/policy-ready.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/refresh-env-var-in-pod/policy-ready.yaml.
CONFLICT (file location): other/refresh-env-var-in-pod/secret.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/refresh-env-var-in-pod/secret.yaml.
CONFLICT (file location): other/refresh-volumes-in-pods/00-crb.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/refresh-volumes-in-pods/00-crb.yaml.
CONFLICT (file location): other/refresh-volumes-in-pods/01-policy.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/refresh-volumes-in-pods/01-policy.yaml.
CONFLICT (file location): other/refresh-volumes-in-pods/02-manifests.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/refresh-volumes-in-pods/02-manifests.yaml.
CONFLICT (file location): other/refresh-volumes-in-pods/03-cm.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/refresh-volumes-in-pods/03-cm.yaml.
CONFLICT (file location): other/refresh-volumes-in-pods/04-check.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/refresh-volumes-in-pods/04-check.yaml.
CONFLICT (file location): other/refresh-volumes-in-pods/cm.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/refresh-volumes-in-pods/cm.yaml.
CONFLICT (file location): other/refresh-volumes-in-pods/ns.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/refresh-volumes-in-pods/ns.yaml.
CONFLICT (file location): other/refresh-volumes-in-pods/policy-ready.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/refresh-volumes-in-pods/policy-ready.yaml.
CONFLICT (file location): other/remove-hostpath-volumes/01-policy.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/remove-hostpath-volumes/01-policy.yaml.
CONFLICT (file location): other/remove-hostpath-volumes/02-manifests.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/remove-hostpath-volumes/02-manifests.yaml.
CONFLICT (file location): other/remove-hostpath-volumes/03-check.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/remove-hostpath-volumes/03-check.yaml.
CONFLICT (file location): other/remove-hostpath-volumes/04-delete.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/remove-hostpath-volumes/04-delete.yaml.
CONFLICT (file location): other/remove-hostpath-volumes/not-pod-patched04.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/remove-hostpath-volumes/not-pod-patched04.yaml.
CONFLICT (file location): other/remove-hostpath-volumes/not-pod-patched05.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/remove-hostpath-volumes/not-pod-patched05.yaml.
CONFLICT (file location): other/remove-hostpath-volumes/ns.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/remove-hostpath-volumes/ns.yaml.
CONFLICT (file location): other/remove-hostpath-volumes/pod-patched.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/remove-hostpath-volumes/pod-patched.yaml.
CONFLICT (file location): other/remove-hostpath-volumes/pod-patched02.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/remove-hostpath-volumes/pod-patched02.yaml.
CONFLICT (file location): other/remove-hostpath-volumes/pod-patched03.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/remove-hostpath-volumes/pod-patched03.yaml.
CONFLICT (file location): other/remove-hostpath-volumes/pod-patched04.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/remove-hostpath-volumes/pod-patched04.yaml.
CONFLICT (file location): other/remove-hostpath-volumes/pods.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/remove-hostpath-volumes/pods.yaml.
CONFLICT (file location): other/remove-hostpath-volumes/policy-ready.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/remove-hostpath-volumes/policy-ready.yaml.
CONFLICT (file location): other/remove-serviceaccount-token/01-policy.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/remove-serviceaccount-token/01-policy.yaml.
CONFLICT (file location): other/remove-serviceaccount-token/02-manifests.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/remove-serviceaccount-token/02-manifests.yaml.
CONFLICT (file location): other/remove-serviceaccount-token/03-check.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/remove-serviceaccount-token/03-check.yaml.
CONFLICT (file location): other/remove-serviceaccount-token/04-delete.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/remove-serviceaccount-token/04-delete.yaml.
CONFLICT (file location): other/remove-serviceaccount-token/ns.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/remove-serviceaccount-token/ns.yaml.
CONFLICT (file location): other/remove-serviceaccount-token/pod-not-patched01.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/remove-serviceaccount-token/pod-not-patched01.yaml.
CONFLICT (file location): other/remove-serviceaccount-token/pod-not-patched02.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/remove-serviceaccount-token/pod-not-patched02.yaml.
CONFLICT (file location): other/remove-serviceaccount-token/pod-patched.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/remove-serviceaccount-token/pod-patched.yaml.
CONFLICT (file location): other/remove-serviceaccount-token/pod-patched02.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/remove-serviceaccount-token/pod-patched02.yaml.
CONFLICT (file location): other/remove-serviceaccount-token/pods.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/remove-serviceaccount-token/pods.yaml.
CONFLICT (file location): other/remove-serviceaccount-token/policy-ready.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/remove-serviceaccount-token/policy-ready.yaml.
CONFLICT (file location): other/replace-image-registry/01-policy.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/replace-image-registry/01-policy.yaml.
CONFLICT (file location): other/replace-image-registry/02-manifests.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/replace-image-registry/02-manifests.yaml.
CONFLICT (file location): other/replace-image-registry/03-delete.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/replace-image-registry/03-delete.yaml.
CONFLICT (file location): other/replace-image-registry/ns.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/replace-image-registry/ns.yaml.
CONFLICT (file location): other/replace-image-registry/pod-patched.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/replace-image-registry/pod-patched.yaml.
CONFLICT (file location): other/replace-image-registry/pod-patched02.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/replace-image-registry/pod-patched02.yaml.
CONFLICT (file location): other/replace-image-registry/pod-patched03.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/replace-image-registry/pod-patched03.yaml.
CONFLICT (file location): other/replace-image-registry/pods.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/replace-image-registry/pods.yaml.
CONFLICT (file location): other/replace-image-registry/policy-ready.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/replace-image-registry/policy-ready.yaml.
CONFLICT (file location): other/require-annotations/01-assert.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-annotations/01-assert.yaml.
CONFLICT (file location): other/require-annotations/01-enforce.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-annotations/01-enforce.yaml.
CONFLICT (file location): other/require-annotations/02-manifests.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-annotations/02-manifests.yaml.
CONFLICT (file location): other/require-annotations/99-delete.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-annotations/99-delete.yaml.
CONFLICT (file location): other/require-annotations/pod-bad.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-annotations/pod-bad.yaml.
CONFLICT (file location): other/require-annotations/pod-good.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-annotations/pod-good.yaml.
CONFLICT (file location): other/require-annotations/podcontroller-bad.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-annotations/podcontroller-bad.yaml.
CONFLICT (file location): other/require-annotations/podcontroller-good.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-annotations/podcontroller-good.yaml.
CONFLICT (file location): other/require-base-image/01-assert.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-base-image/01-assert.yaml.
CONFLICT (file location): other/require-base-image/01-enforce.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-base-image/01-enforce.yaml.
CONFLICT (file location): other/require-base-image/02-manifests.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-base-image/02-manifests.yaml.
CONFLICT (file location): other/require-base-image/99-delete.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-base-image/99-delete.yaml.
CONFLICT (file location): other/require-base-image/ns.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-base-image/ns.yaml.
CONFLICT (file location): other/require-base-image/pod-bad.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-base-image/pod-bad.yaml.
CONFLICT (file location): other/require-base-image/pod-good.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-base-image/pod-good.yaml.
CONFLICT (file location): other/require-base-image/podcontroller-bad.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-base-image/podcontroller-bad.yaml.
CONFLICT (file location): other/require-base-image/podcontroller-good.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-base-image/podcontroller-good.yaml.
CONFLICT (file location): other/require-container-port-names/01-assert.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-container-port-names/01-assert.yaml.
CONFLICT (file location): other/require-container-port-names/01-enforce.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-container-port-names/01-enforce.yaml.
CONFLICT (file location): other/require-container-port-names/02-manifests.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-container-port-names/02-manifests.yaml.
CONFLICT (file location): other/require-container-port-names/99-delete.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-container-port-names/99-delete.yaml.
CONFLICT (file location): other/require-container-port-names/pod-bad.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-container-port-names/pod-bad.yaml.
CONFLICT (file location): other/require-container-port-names/pod-good.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-container-port-names/pod-good.yaml.
CONFLICT (file location): other/require-container-port-names/podcontroller-bad.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-container-port-names/podcontroller-bad.yaml.
CONFLICT (file location): other/require-container-port-names/podcontroller-good.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-container-port-names/podcontroller-good.yaml.
CONFLICT (file location): other/require-deployments-have-multiple-replicas/01-assert.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-deployments-have-multiple-replicas/01-assert.yaml.
CONFLICT (file location): other/require-deployments-have-multiple-replicas/01-enforce.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-deployments-have-multiple-replicas/01-enforce.yaml.
CONFLICT (file location): other/require-deployments-have-multiple-replicas/02-manifests.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-deployments-have-multiple-replicas/02-manifests.yaml.
CONFLICT (file location): other/require-deployments-have-multiple-replicas/99-delete.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-deployments-have-multiple-replicas/99-delete.yaml.
CONFLICT (file location): other/require-deployments-have-multiple-replicas/deploy-bad.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-deployments-have-multiple-replicas/deploy-bad.yaml.
CONFLICT (file location): other/require-deployments-have-multiple-replicas/deploy-good.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-deployments-have-multiple-replicas/deploy-good.yaml.
CONFLICT (file location): other/require-emptydir-requests-limits/01-assert.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-emptydir-requests-limits/01-assert.yaml.
CONFLICT (file location): other/require-emptydir-requests-limits/01-enforce.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-emptydir-requests-limits/01-enforce.yaml.
CONFLICT (file location): other/require-emptydir-requests-limits/02-manifests.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-emptydir-requests-limits/02-manifests.yaml.
CONFLICT (file location): other/require-emptydir-requests-limits/99-delete.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-emptydir-requests-limits/99-delete.yaml.
CONFLICT (file location): other/require-emptydir-requests-limits/bad-pod.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-emptydir-requests-limits/bad-pod.yaml.
CONFLICT (file location): other/require-emptydir-requests-limits/pod-bad.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-emptydir-requests-limits/pod-bad.yaml.
CONFLICT (file location): other/require-emptydir-requests-limits/pod-good.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-emptydir-requests-limits/pod-good.yaml.
CONFLICT (file location): other/require-emptydir-requests-limits/podcontroller-bad.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-emptydir-requests-limits/podcontroller-bad.yaml.
CONFLICT (file location): other/require-emptydir-requests-limits/podcontroller-good.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-emptydir-requests-limits/podcontroller-good.yaml.
CONFLICT (file location): other/require-image-checksum/01-assert.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-image-checksum/01-assert.yaml.
CONFLICT (file location): other/require-image-checksum/01-enforce.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-image-checksum/01-enforce.yaml.
CONFLICT (file location): other/require-image-checksum/02-manifests.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-image-checksum/02-manifests.yaml.
CONFLICT (file location): other/require-image-checksum/99-delete.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-image-checksum/99-delete.yaml.
CONFLICT (file location): other/require-image-checksum/pod-bad.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-image-checksum/pod-bad.yaml.
CONFLICT (file location): other/require-image-checksum/pod-good.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-image-checksum/pod-good.yaml.
CONFLICT (file location): other/require-image-checksum/podcontroller-bad.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-image-checksum/podcontroller-bad.yaml.
CONFLICT (file location): other/require-image-checksum/podcontroller-good.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-image-checksum/podcontroller-good.yaml.
CONFLICT (file location): other/require-image-source/01-assert.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-image-source/01-assert.yaml.
CONFLICT (file location): other/require-image-source/01-enforce.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-image-source/01-enforce.yaml.
CONFLICT (file location): other/require-image-source/02-manifests.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-image-source/02-manifests.yaml.
CONFLICT (file location): other/require-image-source/99-delete.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-image-source/99-delete.yaml.
CONFLICT (file location): other/require-image-source/pod-bad.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-image-source/pod-bad.yaml.
CONFLICT (file location): other/require-image-source/pod-good.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-image-source/pod-good.yaml.
CONFLICT (file location): other/require-image-source/podcontroller-bad.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-image-source/podcontroller-bad.yaml.
CONFLICT (file location): other/require-image-source/podcontroller-good.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-image-source/podcontroller-good.yaml.
CONFLICT (file location): other/require-imagepullsecrets/01-assert.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-imagepullsecrets/01-assert.yaml.
CONFLICT (file location): other/require-imagepullsecrets/01-enforce.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-imagepullsecrets/01-enforce.yaml.
CONFLICT (file location): other/require-imagepullsecrets/02-manifests.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-imagepullsecrets/02-manifests.yaml.
CONFLICT (file location): other/require-imagepullsecrets/99-delete.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-imagepullsecrets/99-delete.yaml.
CONFLICT (file location): other/require-imagepullsecrets/pod-bad.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-imagepullsecrets/pod-bad.yaml.
CONFLICT (file location): other/require-imagepullsecrets/pod-good.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-imagepullsecrets/pod-good.yaml.
CONFLICT (file location): other/require-imagepullsecrets/podcontroller-bad.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-imagepullsecrets/podcontroller-bad.yaml.
CONFLICT (file location): other/require-imagepullsecrets/podcontroller-good.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-imagepullsecrets/podcontroller-good.yaml.
CONFLICT (file location): other/require-ingress-https/01-assert.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-ingress-https/01-assert.yaml.
CONFLICT (file location): other/require-ingress-https/01-enforce.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-ingress-https/01-enforce.yaml.
CONFLICT (file location): other/require-ingress-https/02-manifests.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-ingress-https/02-manifests.yaml.
CONFLICT (file location): other/require-ingress-https/99-delete.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-ingress-https/99-delete.yaml.
CONFLICT (file location): other/require-ingress-https/ingress-bad.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-ingress-https/ingress-bad.yaml.
CONFLICT (file location): other/require-ingress-https/ingress-good.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-ingress-https/ingress-good.yaml.
CONFLICT (file location): other/require-netpol/01-assert.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-netpol/01-assert.yaml.
CONFLICT (file location): other/require-netpol/01-enforce.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-netpol/01-enforce.yaml.
CONFLICT (file location): other/require-netpol/02-manifests.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-netpol/02-manifests.yaml.
CONFLICT (file location): other/require-netpol/99-delete.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-netpol/99-delete.yaml.
CONFLICT (file location): other/require-netpol/deploy-bad.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-netpol/deploy-bad.yaml.
CONFLICT (file location): other/require-netpol/deploy-good.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-netpol/deploy-good.yaml.
CONFLICT (file location): other/require-netpol/netpol.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-netpol/netpol.yaml.
CONFLICT (file location): other/require-non-root-groups/01-assert.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-non-root-groups/01-assert.yaml.
CONFLICT (file location): other/require-non-root-groups/01-enforce.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-non-root-groups/01-enforce.yaml.
CONFLICT (file location): other/require-non-root-groups/02-manifests.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-non-root-groups/02-manifests.yaml.
CONFLICT (file location): other/require-non-root-groups/99-delete.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-non-root-groups/99-delete.yaml.
CONFLICT (file location): other/require-non-root-groups/pod-bad.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-non-root-groups/pod-bad.yaml.
CONFLICT (file location): other/require-non-root-groups/pod-good.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-non-root-groups/pod-good.yaml.
CONFLICT (file location): other/require-non-root-groups/podcontroller-bad.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-non-root-groups/podcontroller-bad.yaml.
CONFLICT (file location): other/require-non-root-groups/podcontroller-good.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-non-root-groups/podcontroller-good.yaml.
CONFLICT (file location): other/require-pdb/01-assert.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-pdb/01-assert.yaml.
CONFLICT (file location): other/require-pdb/01-enforce.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-pdb/01-enforce.yaml.
CONFLICT (file location): other/require-pdb/02-manifests.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-pdb/02-manifests.yaml.
CONFLICT (file location): other/require-pdb/99-delete.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-pdb/99-delete.yaml.
CONFLICT (file location): other/require-pdb/deploy-bad.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-pdb/deploy-bad.yaml.
CONFLICT (file location): other/require-pdb/deploy-good.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-pdb/deploy-good.yaml.
CONFLICT (file location): other/require-pdb/pdb.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-pdb/pdb.yaml.
CONFLICT (file location): other/require-pdb/ss-bad.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-pdb/ss-bad.yaml.
CONFLICT (file location): other/require-pdb/ss-good.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-pdb/ss-good.yaml.
CONFLICT (file location): other/require-pod-priorityclassname/01-policy.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-pod-priorityclassname/01-policy.yaml.
CONFLICT (file location): other/require-pod-priorityclassname/02-manifests.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-pod-priorityclassname/02-manifests.yaml.
CONFLICT (file location): other/require-pod-priorityclassname/pc.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-pod-priorityclassname/pc.yaml.
CONFLICT (file location): other/require-pod-priorityclassname/pod-bad.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-pod-priorityclassname/pod-bad.yaml.
CONFLICT (file location): other/require-pod-priorityclassname/pod-good.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-pod-priorityclassname/pod-good.yaml.
CONFLICT (file location): other/require-pod-priorityclassname/podcontroller-bad.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-pod-priorityclassname/podcontroller-bad.yaml.
CONFLICT (file location): other/require-pod-priorityclassname/podcontroller-good.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-pod-priorityclassname/podcontroller-good.yaml.
CONFLICT (file location): other/require-pod-priorityclassname/policy-ready.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-pod-priorityclassname/policy-ready.yaml.
CONFLICT (file location): other/require-qos-burstable/01-assert.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-qos-burstable/01-assert.yaml.
CONFLICT (file location): other/require-qos-burstable/01-enforce.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-qos-burstable/01-enforce.yaml.
CONFLICT (file location): other/require-qos-burstable/02-manifests.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-qos-burstable/02-manifests.yaml.
CONFLICT (file location): other/require-qos-burstable/99-delete.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-qos-burstable/99-delete.yaml.
CONFLICT (file location): other/require-qos-burstable/pod-bad.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-qos-burstable/pod-bad.yaml.
CONFLICT (file location): other/require-qos-burstable/pod-good.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-qos-burstable/pod-good.yaml.
CONFLICT (file location): other/require-qos-burstable/podcontroller-bad.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-qos-burstable/podcontroller-bad.yaml.
CONFLICT (file location): other/require-qos-burstable/podcontroller-good.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-qos-burstable/podcontroller-good.yaml.
CONFLICT (file location): other/require-qos-guaranteed/01-assert.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-qos-guaranteed/01-assert.yaml.
CONFLICT (file location): other/require-qos-guaranteed/01-enforce.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-qos-guaranteed/01-enforce.yaml.
CONFLICT (file location): other/require-qos-guaranteed/02-manifests.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-qos-guaranteed/02-manifests.yaml.
CONFLICT (file location): other/require-qos-guaranteed/99-delete.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-qos-guaranteed/99-delete.yaml.
CONFLICT (file location): other/require-qos-guaranteed/pod-bad.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-qos-guaranteed/pod-bad.yaml.
CONFLICT (file location): other/require-qos-guaranteed/pod-good.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-qos-guaranteed/pod-good.yaml.
CONFLICT (file location): other/require-qos-guaranteed/podcontroller-bad.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-qos-guaranteed/podcontroller-bad.yaml.
CONFLICT (file location): other/require-qos-guaranteed/podcontroller-good.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-qos-guaranteed/podcontroller-good.yaml.
CONFLICT (file location): other/require-storageclass/01-assert.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-storageclass/01-assert.yaml.
CONFLICT (file location): other/require-storageclass/01-enforce.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-storageclass/01-enforce.yaml.
CONFLICT (file location): other/require-storageclass/02-manifests.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-storageclass/02-manifests.yaml.
CONFLICT (file location): other/require-storageclass/99-delete.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-storageclass/99-delete.yaml.
CONFLICT (file location): other/require-storageclass/pvc-bad.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-storageclass/pvc-bad.yaml.
CONFLICT (file location): other/require-storageclass/pvc-good.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-storageclass/pvc-good.yaml.
CONFLICT (file location): other/require-storageclass/ss-bad.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-storageclass/ss-bad.yaml.
CONFLICT (file location): other/require-storageclass/ss-good.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-storageclass/ss-good.yaml.
CONFLICT (file location): other/require-unique-external-dns/01-assert.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-unique-external-dns/01-assert.yaml.
CONFLICT (file location): other/require-unique-external-dns/01-enforce.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-unique-external-dns/01-enforce.yaml.
CONFLICT (file location): other/require-unique-external-dns/02-manifests.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-unique-external-dns/02-manifests.yaml.
CONFLICT (file location): other/require-unique-external-dns/99-delete.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-unique-external-dns/99-delete.yaml.
CONFLICT (file location): other/require-unique-external-dns/svc-bad.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-unique-external-dns/svc-bad.yaml.
CONFLICT (file location): other/require-unique-external-dns/svc-good.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-unique-external-dns/svc-good.yaml.
CONFLICT (file location): other/require-unique-external-dns/svc.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-unique-external-dns/svc.yaml.
CONFLICT (file location): other/require-unique-service-selector/01-assert.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-unique-service-selector/01-assert.yaml.
CONFLICT (file location): other/require-unique-service-selector/01-enforce.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-unique-service-selector/01-enforce.yaml.
CONFLICT (file location): other/require-unique-service-selector/02-manifests.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-unique-service-selector/02-manifests.yaml.
CONFLICT (file location): other/require-unique-service-selector/99-delete.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-unique-service-selector/99-delete.yaml.
CONFLICT (file location): other/require-unique-service-selector/svc-bad.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-unique-service-selector/svc-bad.yaml.
CONFLICT (file location): other/require-unique-service-selector/svc-good.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-unique-service-selector/svc-good.yaml.
CONFLICT (file location): other/require-unique-service-selector/svc.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-unique-service-selector/svc.yaml.
CONFLICT (file location): other/require-unique-uid-per-workload/01-assert.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-unique-uid-per-workload/01-assert.yaml.
CONFLICT (file location): other/require-unique-uid-per-workload/01-enforce.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-unique-uid-per-workload/01-enforce.yaml.
CONFLICT (file location): other/require-unique-uid-per-workload/02-manifests.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-unique-uid-per-workload/02-manifests.yaml.
CONFLICT (file location): other/require-unique-uid-per-workload/99-delete.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-unique-uid-per-workload/99-delete.yaml.
CONFLICT (file location): other/require-unique-uid-per-workload/pod-bad.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-unique-uid-per-workload/pod-bad.yaml.
CONFLICT (file location): other/require-unique-uid-per-workload/pod-good.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-unique-uid-per-workload/pod-good.yaml.
CONFLICT (file location): other/require-unique-uid-per-workload/pods.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/rec-req/require-unique-uid-per-workload/pods.yaml.
CONFLICT (file location): other/resolve-image-to-digest/01-policy.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/resolve-image-to-digest/01-policy.yaml.
CONFLICT (file location): other/resolve-image-to-digest/02-manifests.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/resolve-image-to-digest/02-manifests.yaml.
CONFLICT (file location): other/resolve-image-to-digest/podcontroller-patched.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/resolve-image-to-digest/podcontroller-patched.yaml.
CONFLICT (file location): other/resolve-image-to-digest/podcontroller.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/resolve-image-to-digest/podcontroller.yaml.
CONFLICT (file location): other/resolve-image-to-digest/pods-patched.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/resolve-image-to-digest/pods-patched.yaml.
CONFLICT (file location): other/resolve-image-to-digest/pods.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/resolve-image-to-digest/pods.yaml.
CONFLICT (file location): other/resolve-image-to-digest/policy-ready.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/resolve-image-to-digest/policy-ready.yaml.
CONFLICT (file location): other/restart-deployment-on-secret-change/01-manifests.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restart-deployment-on-secret-change/01-manifests.yaml.
CONFLICT (file location): other/restart-deployment-on-secret-change/02-policy.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restart-deployment-on-secret-change/02-policy.yaml.
CONFLICT (file location): other/restart-deployment-on-secret-change/03-update-sc.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restart-deployment-on-secret-change/03-update-sc.yaml.
CONFLICT (file location): other/restart-deployment-on-secret-change/04-check.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restart-deployment-on-secret-change/04-check.yaml.
CONFLICT (file location): other/restart-deployment-on-secret-change/cluster-role.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restart-deployment-on-secret-change/cluster-role.yaml.
CONFLICT (file location): other/restart-deployment-on-secret-change/deploy.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restart-deployment-on-secret-change/deploy.yaml.
CONFLICT (file location): other/restart-deployment-on-secret-change/policy-ready.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restart-deployment-on-secret-change/policy-ready.yaml.
CONFLICT (file location): other/restart-deployment-on-secret-change/secret.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restart-deployment-on-secret-change/secret.yaml.
CONFLICT (file location): other/restrict-annotations/01-assert.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-annotations/01-assert.yaml.
CONFLICT (file location): other/restrict-annotations/01-enforce.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-annotations/01-enforce.yaml.
CONFLICT (file location): other/restrict-annotations/02-manifests.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-annotations/02-manifests.yaml.
CONFLICT (file location): other/restrict-annotations/99-delete.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-annotations/99-delete.yaml.
CONFLICT (file location): other/restrict-annotations/pod-bad.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-annotations/pod-bad.yaml.
CONFLICT (file location): other/restrict-annotations/pod-good.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-annotations/pod-good.yaml.
CONFLICT (file location): other/restrict-annotations/podcontroller-bad.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-annotations/podcontroller-bad.yaml.
CONFLICT (file location): other/restrict-annotations/podcontroller-good.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-annotations/podcontroller-good.yaml.
CONFLICT (file location): other/restrict-automount-sa-token/01-assert.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-automount-sa-token/01-assert.yaml.
CONFLICT (file location): other/restrict-automount-sa-token/01-enforce.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-automount-sa-token/01-enforce.yaml.
CONFLICT (file location): other/restrict-automount-sa-token/02-manifests.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-automount-sa-token/02-manifests.yaml.
CONFLICT (file location): other/restrict-automount-sa-token/99-delete.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-automount-sa-token/99-delete.yaml.
CONFLICT (file location): other/restrict-automount-sa-token/pod-bad.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-automount-sa-token/pod-bad.yaml.
CONFLICT (file location): other/restrict-automount-sa-token/pod-good.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-automount-sa-token/pod-good.yaml.
CONFLICT (file location): other/restrict-automount-sa-token/podcontroller-bad.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-automount-sa-token/podcontroller-bad.yaml.
CONFLICT (file location): other/restrict-automount-sa-token/podcontroller-good.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-automount-sa-token/podcontroller-good.yaml.
CONFLICT (file location): other/restrict-binding-clusteradmin/01-assert.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-binding-clusteradmin/01-assert.yaml.
CONFLICT (file location): other/restrict-binding-clusteradmin/01-enforce.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-binding-clusteradmin/01-enforce.yaml.
CONFLICT (file location): other/restrict-binding-clusteradmin/02-manifests.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-binding-clusteradmin/02-manifests.yaml.
CONFLICT (file location): other/restrict-binding-clusteradmin/99-delete.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-binding-clusteradmin/99-delete.yaml.
CONFLICT (file location): other/restrict-binding-clusteradmin/crb-bad.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-binding-clusteradmin/crb-bad.yaml.
CONFLICT (file location): other/restrict-binding-clusteradmin/crb-good.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-binding-clusteradmin/crb-good.yaml.
CONFLICT (file location): other/restrict-binding-clusteradmin/rb-bad.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-binding-clusteradmin/rb-bad.yaml.
CONFLICT (file location): other/restrict-binding-clusteradmin/rb-good.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-binding-clusteradmin/rb-good.yaml.
CONFLICT (file location): other/restrict-binding-system-groups/01-assert.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-binding-system-groups/01-assert.yaml.
CONFLICT (file location): other/restrict-binding-system-groups/01-enforce.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-binding-system-groups/01-enforce.yaml.
CONFLICT (file location): other/restrict-binding-system-groups/02-manifests.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-binding-system-groups/02-manifests.yaml.
CONFLICT (file location): other/restrict-binding-system-groups/99-delete.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-binding-system-groups/99-delete.yaml.
CONFLICT (file location): other/restrict-binding-system-groups/crb-bad.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-binding-system-groups/crb-bad.yaml.
CONFLICT (file location): other/restrict-binding-system-groups/crb-good.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-binding-system-groups/crb-good.yaml.
CONFLICT (file location): other/restrict-binding-system-groups/rb-bad.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-binding-system-groups/rb-bad.yaml.
CONFLICT (file location): other/restrict-binding-system-groups/rb-good.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-binding-system-groups/rb-good.yaml.
CONFLICT (file location): other/restrict-clusterrole-nodesproxy/01-assert.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-clusterrole-nodesproxy/01-assert.yaml.
CONFLICT (file location): other/restrict-clusterrole-nodesproxy/01-enforce.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-clusterrole-nodesproxy/01-enforce.yaml.
CONFLICT (file location): other/restrict-clusterrole-nodesproxy/02-manifests.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-clusterrole-nodesproxy/02-manifests.yaml.
CONFLICT (file location): other/restrict-clusterrole-nodesproxy/99-delete.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-clusterrole-nodesproxy/99-delete.yaml.
CONFLICT (file location): other/restrict-clusterrole-nodesproxy/cr-bad.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-clusterrole-nodesproxy/cr-bad.yaml.
CONFLICT (file location): other/restrict-clusterrole-nodesproxy/cr-good.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-clusterrole-nodesproxy/cr-good.yaml.
CONFLICT (file location): other/restrict-controlplane-scheduling/01-assert.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-controlplane-scheduling/01-assert.yaml.
CONFLICT (file location): other/restrict-controlplane-scheduling/01-enforce.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-controlplane-scheduling/01-enforce.yaml.
CONFLICT (file location): other/restrict-controlplane-scheduling/02-manifests.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-controlplane-scheduling/02-manifests.yaml.
CONFLICT (file location): other/restrict-controlplane-scheduling/99-delete.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-controlplane-scheduling/99-delete.yaml.
CONFLICT (file location): other/restrict-controlplane-scheduling/pod-bad.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-controlplane-scheduling/pod-bad.yaml.
CONFLICT (file location): other/restrict-controlplane-scheduling/pod-good.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-controlplane-scheduling/pod-good.yaml.
CONFLICT (file location): other/restrict-controlplane-scheduling/podcontroller-bad.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-controlplane-scheduling/podcontroller-bad.yaml.
CONFLICT (file location): other/restrict-controlplane-scheduling/podcontroller-good.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-controlplane-scheduling/podcontroller-good.yaml.
CONFLICT (file location): other/restrict-deprecated-registry/01-policy.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-deprecated-registry/01-policy.yaml.
CONFLICT (file location): other/restrict-deprecated-registry/02-manifests.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-deprecated-registry/02-manifests.yaml.
CONFLICT (file location): other/restrict-deprecated-registry/ns.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-deprecated-registry/ns.yaml.
CONFLICT (file location): other/restrict-deprecated-registry/pod-bad.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-deprecated-registry/pod-bad.yaml.
CONFLICT (file location): other/restrict-deprecated-registry/pod-good.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-deprecated-registry/pod-good.yaml.
CONFLICT (file location): other/restrict-deprecated-registry/podcontroller-bad.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-deprecated-registry/podcontroller-bad.yaml.
CONFLICT (file location): other/restrict-deprecated-registry/podcontroller-good.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-deprecated-registry/podcontroller-good.yaml.
CONFLICT (file location): other/restrict-deprecated-registry/policy-ready.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-deprecated-registry/policy-ready.yaml.
CONFLICT (file location): other/restrict-escalation-verbs-roles/01-assert.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-escalation-verbs-roles/01-assert.yaml.
CONFLICT (file location): other/restrict-escalation-verbs-roles/01-enforce.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-escalation-verbs-roles/01-enforce.yaml.
CONFLICT (file location): other/restrict-escalation-verbs-roles/02-manifests.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-escalation-verbs-roles/02-manifests.yaml.
CONFLICT (file location): other/restrict-escalation-verbs-roles/99-delete.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-escalation-verbs-roles/99-delete.yaml.
CONFLICT (file location): other/restrict-escalation-verbs-roles/cr-bad.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-escalation-verbs-roles/cr-bad.yaml.
CONFLICT (file location): other/restrict-escalation-verbs-roles/cr-good.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-escalation-verbs-roles/cr-good.yaml.
CONFLICT (file location): other/restrict-escalation-verbs-roles/role-bad.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-escalation-verbs-roles/role-bad.yaml.
CONFLICT (file location): other/restrict-escalation-verbs-roles/role-good.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-escalation-verbs-roles/role-good.yaml.
CONFLICT (file location): other/restrict-ingress-classes/01-assert.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-ingress-classes/01-assert.yaml.
CONFLICT (file location): other/restrict-ingress-classes/01-enforce.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-ingress-classes/01-enforce.yaml.
CONFLICT (file location): other/restrict-ingress-classes/02-manifests.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-ingress-classes/02-manifests.yaml.
CONFLICT (file location): other/restrict-ingress-classes/99-delete.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-ingress-classes/99-delete.yaml.
CONFLICT (file location): other/restrict-ingress-classes/ingress-bad.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-ingress-classes/ingress-bad.yaml.
CONFLICT (file location): other/restrict-ingress-classes/ingress-good.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-ingress-classes/ingress-good.yaml.
CONFLICT (file location): other/restrict-ingress-defaultbackend/01-assert.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-ingress-defaultbackend/01-assert.yaml.
CONFLICT (file location): other/restrict-ingress-defaultbackend/01-enforce.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-ingress-defaultbackend/01-enforce.yaml.
CONFLICT (file location): other/restrict-ingress-defaultbackend/02-manifests.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-ingress-defaultbackend/02-manifests.yaml.
CONFLICT (file location): other/restrict-ingress-defaultbackend/99-delete.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-ingress-defaultbackend/99-delete.yaml.
CONFLICT (file location): other/restrict-ingress-defaultbackend/ingress-bad.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-ingress-defaultbackend/ingress-bad.yaml.
CONFLICT (file location): other/restrict-ingress-defaultbackend/ingress-good.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-ingress-defaultbackend/ingress-good.yaml.
CONFLICT (file location): other/restrict-ingress-host/01-assert.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-ingress-host/01-assert.yaml.
CONFLICT (file location): other/restrict-ingress-host/01-enforce.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-ingress-host/01-enforce.yaml.
CONFLICT (file location): other/restrict-ingress-host/02-manifests.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-ingress-host/02-manifests.yaml.
CONFLICT (file location): other/restrict-ingress-host/99-delete.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-ingress-host/99-delete.yaml.
CONFLICT (file location): other/restrict-ingress-host/ingress-bad.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-ingress-host/ingress-bad.yaml.
CONFLICT (file location): other/restrict-ingress-host/ingress-good.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-ingress-host/ingress-good.yaml.
CONFLICT (file location): other/restrict-ingress-host/ingress.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-ingress-host/ingress.yaml.
CONFLICT (file location): other/restrict-ingress-wildcard/01-assert.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-ingress-wildcard/01-assert.yaml.
CONFLICT (file location): other/restrict-ingress-wildcard/01-enforce.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-ingress-wildcard/01-enforce.yaml.
CONFLICT (file location): other/restrict-ingress-wildcard/02-manifests.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-ingress-wildcard/02-manifests.yaml.
CONFLICT (file location): other/restrict-ingress-wildcard/99-delete.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-ingress-wildcard/99-delete.yaml.
CONFLICT (file location): other/restrict-ingress-wildcard/ingress-bad.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-ingress-wildcard/ingress-bad.yaml.
CONFLICT (file location): other/restrict-ingress-wildcard/ingress-good.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-ingress-wildcard/ingress-good.yaml.
CONFLICT (file location): other/restrict-jobs/01-policy.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-jobs/01-policy.yaml.
CONFLICT (file location): other/restrict-jobs/02-manifests.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-jobs/02-manifests.yaml.
CONFLICT (file location): other/restrict-jobs/cronjobs-good.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-jobs/cronjobs-good.yaml.
CONFLICT (file location): other/restrict-jobs/jobs-bad.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-jobs/jobs-bad.yaml.
CONFLICT (file location): other/restrict-jobs/policy-ready.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-jobs/policy-ready.yaml.
CONFLICT (file location): other/restrict-loadbalancer/01-assert.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-loadbalancer/01-assert.yaml.
CONFLICT (file location): other/restrict-loadbalancer/01-enforce.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-loadbalancer/01-enforce.yaml.
CONFLICT (file location): other/restrict-loadbalancer/02-manifests.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-loadbalancer/02-manifests.yaml.
CONFLICT (file location): other/restrict-loadbalancer/99-delete.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-loadbalancer/99-delete.yaml.
CONFLICT (file location): other/restrict-loadbalancer/svc-bad.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-loadbalancer/svc-bad.yaml.
CONFLICT (file location): other/restrict-loadbalancer/svc-good.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-loadbalancer/svc-good.yaml.
CONFLICT (file location): other/restrict-networkpolicy-empty-podselector/01-assert.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-networkpolicy-empty-podselector/01-assert.yaml.
CONFLICT (file location): other/restrict-networkpolicy-empty-podselector/01-enforce.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-networkpolicy-empty-podselector/01-enforce.yaml.
CONFLICT (file location): other/restrict-networkpolicy-empty-podselector/02-manifests.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-networkpolicy-empty-podselector/02-manifests.yaml.
CONFLICT (file location): other/restrict-networkpolicy-empty-podselector/99-delete.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-networkpolicy-empty-podselector/99-delete.yaml.
CONFLICT (file location): other/restrict-networkpolicy-empty-podselector/netpol-bad.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-networkpolicy-empty-podselector/netpol-bad.yaml.
CONFLICT (file location): other/restrict-networkpolicy-empty-podselector/netpol-good.yaml added in origin/main inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to other/res/restrict-networkpolicy-empty-podselector/netpol-good.yaml.
Automatic merge failed; fix conflicts and then commit the result.

How to fix?

I'd just close this PR, ensure your fork is up-to-date, then go through the normal branching and PR process again.

OK I'll do that 👍🏻

@chipzoller Made a new PR. Have a look


Increase timeout for big backup creation

https://github.com/longhorn/longhorn/issues/1721
The timeout for waiting for backup to be created successfully is increased to 10 mins from 5 mins as backup creation takes ~8 mins to complete if the data size is about 800 Mi.

LGTM


Feauture Request: Critical Path

Can you please add functionality to indicate the critical path of a project? Thank you.

Could you explain @Mashiane?


Can't switch on from Harmony

The Harmony is sending color, bright and on state.
The habridge says that there is no color and no bright.
But the on state will not be processed
The color and brightness are not parameterized
Version: 5.2.2. rc4
04-28-2019 17:08:15.108 | INFO | Dim url not available for state change, lightId: 3, userId: b24aed0f532c4752a14931e7ca1d9b80, from IP: <IP_ADDRESS>, body: {"xy":[0,0],"on":true,"bri":252} | com.bwssystems.HABridge.hue.HueMulator
04-28-2019 17:08:15.109 | INFO | Color url not available for state change, lightId: 3, userId: b24aed0f532c4752a14931e7ca1d9b80, from IP: <IP_ADDRESS>, body: {"xy":[0,0],"on":true,"bri":252} | com.bwssystems.HABridge.hue.HueMulator

There are 2 settings in the device when you edit a shown below:

On when Dim is present (Always uses on with a dim request otherwise it will ignore a given on was well. This is overidden by onFirstDim.)
false

On with First Dim (If the device is not on in the ha-bridge state, it will send on instead of the dim.)
false

The setting "On when Dim is present" needs to be selected for this to work for the harmony.


Migrate to dynamic library linking for linux, effectively supporting systems without X11.

Currently using the XLib and XInput2 requires the overhead of installing the required lib to generate the headers which does not let non-linux host or one without these libs to build the project for those platform.
Second most important thing is that where there is non-X11 desktop environment the library won't work. Which limits it in the amount of targets.
Future plan is to migrate all the c-interop generated stubs into dlopen/dlsym/dlclose Posix API which allows to dynamically fetch the CPointer<CFunction<*>> and invoke it. Which can be done in the runtime (and has pretty less runtime overhead), we may even cache it at the first access.
This will let the library to be build without headers and in Windows/Mac for Linux as well and and can easily test it remotely on a VM. This will also enable to fallback to the Linux device API (/dev/uinput | /dev/input/xxx) if X11 is not present, which will allow the lib to support almost all the linux platforms (though this device API requires superuser).

Fixed with commit 92027738f2093b7cc71c4693bcbc565aec26d206


discreet log contracts for lightning payment channels

We created a high level overview of how DLCs can be used to mitigate the free option problem by creating CFDs.
I am not completely sure where you want to go with this repo but maybe our result / text can be one of the specifications of how to do DLCs in lightning:
https://hackmd.io/@lpQxZaCeTG6OJZI3awxQPQ/LN-DLC

Hi Rene! Thanks for this :)
Could you elaborate a little on how this could be used to mitigate the free option problem? It is my understanding that this name is usually used when discussing the possibility of a multi-asset lightning network, but seeing as this proposal doesn't involve routing is the free option problem still an issue when using rainbow/synthetic assets?

Also potentially relevant to future steps for LN + DLC integration once we have payment points is that we can route DLCs and compose them with other payment point magic, also contract re-negotiation/selling: https://lists.linuxfoundation.org/pipermail/lightning-dev/2019-October/002234.html

Using DLCs on an existing lightning payment channel might be expensive and fragile at scale - at least, it would be if we implement DLCs+LN in the same way described in Dryja's original paper.
If a channel between two peers is used for normal Lightning Network payments while a DLC funding output is pending on the channel, the commitment transaction's TXID will change. This would invalidate the existing set of Adaptor-Signed CETs which spent from that commitment transaction.
Renegotiation
The channel peers must exchange a whole new set of CETs and Adaptor Signatures for every possible Oracle outcome over every DLC output in the channel, before signing a new commitment transaction for that channel. If this complex process cannot be completed, the commitment transaction cannot be signed and the payment will fail. Peers would need to do this twice for every payment: once to produce the commitment transaction with the LN payment's HTLC output, and another to produce the commitment transaction which unwinds the resolved HTLC payment into the channel balance outputs.
To "renegotiate" a DLC with $n$ possible outcomes, each party must construct $n$ CETs, compute $n$ Adaptor Signatures, and verify $n$ Adaptor Signatures, plus the refund transaction and its signatures. If a channel routes $p$ payments per second, this means both channel peers must construct, verify, and exchange $2p(n+1)$ transactions and signatures per second in addition to the existing overhead required for Lightning Network channel state updates. This complexity scales linearly for each pre-existing DLC output in the commitment transaction.
If a Lightning Network channel's commitment transactions are co-populated with a large number of DLC funding outputs, payments over that channel become slower and more expensive, both computationally and financially, because node operator could adjust their per-channel fee rates to match their computational expenditures. It's not unreasonable to foresee that if DLCs become popular tools on LN channels, a single channel might have dozens or hundreds of small DLC outputs locking up funds at any given time. Unlike payment HTLC outputs, a DLC output needs to stick around in the commitment TX output set until the oracle attests to an outcome, which could take weeks or months. Each DLC output might have hundreds or even thousands of CETs which would need to be re-signed twice for every payment through the channel.
I'm not sure at what point this "DLC-renegotiation" process would become unsustainable, but it does seem like a worthwhile consideration in choosing how we implement DLCs on Lightning.

How to resolve this? One naive way we could get binary outcomes to work would be if the commitment transaction pays out to a multisignature address which is a 1-of-2 multisig. The spending condition would basically be:
(alice && outcome_1_key) || (bob && outcome_2_key)

But this would be woefully disappointing. We've lost the opportunities of payout curves - now the contract is just an all-or-nothing wager with no chance for refund if the oracle goes bye-bye. And we haven't saved much computation by doing this - A contract like this as a normal DLC would only require 2 CETs to be renegotiated anyway.
I can't immediately think of any way (even a naive way) to avoid renegotiating while keeping all the nice properties of full-scale DLCs. If the commitment TXID changes unpredictably, there's no way to maintain the validity of child transactions which spend from it, which means the thousands of off-chain pre-signed CETs cannot remain valid.

Hi @conduition ,
great to see that you are picking up this topic. We went down this path some time ago and built a PoC which adds the DLC directly to the commit transaction.
After talking to @Tibo-lg we came to the conclusion that this is not economically feasible if you run a routing node at the same time or if you have several DLCs created in a short period of time.
Simplifying the DLC (e.g. using binary options) would definitely help but this takes away the fun... right? :D
@Tibo-lg came up with a great solution where he adds a split transaction into the mix which splits the original lightning channel into a lightning channel and a DLC channel. Both can then be updated independently.
He wrote a great article about this here: https://medium.com/crypto-garage/dlc-on-lightning-cb5d191f6e64
We wrote about our approach here: https://10101.substack.com/p/noncustodial-trading-with-10101
Eventually we went with Tibo's approach and are currently implementing it in https://github.com/get10101/10101/. Our launch is imminent :D

Thanks @bonomat, I appreciate the extra links. Splitting the channel is a very clever idea, not without drawbacks of course but for the purposes of reusing an existing lightning channel it meets the basic requirements.
I've been thinking about a way to enable off-chain routed DLCs which sounds similar to what 10101 is doing. The blog post from Thibaut describes the protocol for two parties to split a LN channel, which was very helpful. Your own substack post doesn't go into detail on how 10101 routes DLCs between peers. Is there anywhere I can read more about 10101's architecture? Where would i look to discuss a subject like this?

I've been thinking about a way to enable off-chain routed DLCs

AFAIK there is no really good way to enable routed DLCs, the only proposal I'm aware of is this one which requires PTLCs, is IMHO quite restrictive and requires a barrier escrow. If you have a better proposal I'd love to hear it!

@Tibo-lg Thanks for that! I'll take a closer look at that post soon as it has lots of tasty details i'd like to digest.
In the meantime I discovered the dlc-dev mailing list and sent out a summary of my high-level concept there. Although in this email i was omitting the concrete mechanics of setting up the routed DLC as I haven't yet formalized the steps. In theory it should be doable by working from the outside inward. Will post more once i have some time


Update assign-pr owners

This updates assign-pr owners, to have product owners to be reviewers.
Individual GitHub usernames are added per internal wiki instructions.
Actions are rebuilt per instruction above:
cloudflare-docs $  cd .github/actions/assign-issue
cloudflare-docs/.github/actions/assign-issue $  npm install
cloudflare-docs/.github/actions/assign-issue $  npm run build

cloudflare-docs/.github/actions/assign-issue $  cd ../assign-pr
cloudflare-docs/.github/actions/assign-pr $  npm install
cloudflare-docs/.github/actions/assign-pr $  npm run build

Also, .github/CODEOWNERS.backup is updated to keep it in sync for Analytics and Logs section.

@soheiokamoto I updated the PR description so that we don't disclose internal URLs in PR descriptions.

Thanks @pedrosousa for updating PR description. I have updated the commit message as well.
Removed bharatnc for now, as this user has not joined Cloudflare contributor group yet.

Rebased and regenerated index.js fiiles.

Since @bharatnc is now a contributor and recognized here, added him for both projects.
Regenerated index.js.
Ready to merge and test.

LGTM! Going ahead and merging this PR.

It seems like now we are all pulled into all PRs: https://github.com/cloudflare/cloudflare-docs/pulls?q=is%3Apr+user-review-requested%3Asoheiokamoto

This is the issue: https://github.com/cloudflare/cloudflare-docs/blob/b603dedb12e2cf71b7df858f190ac5c781902b61/.github/actions/assign-pr/index.ts#L75-L102
Everyone in owners.ts is treated as PCX authors, and whenever one of this PCX owner opens a PR, everyone is assigned.

What do you think of a fix like this? https://github.com/cloudflare/cloudflare-docs/pull/5612


Undefined name 'init' in actor.py

flake8 testing of https://github.com/hzwer/LearningToPaint on Python 3.7.1
$ flake8 . --count --select=E9,F63,F72,F82 --show-source --statistics
./baseline/DRL/actor.py:17:9: F821 undefined name 'init'
        init.xavier_uniform(m.weight, gain=np.sqrt(2))
        ^
./baseline/DRL/actor.py:18:9: F821 undefined name 'init'
        init.constant(m.bias, 0)
        ^
2     F821 undefined name 'init'
2

E901,E999,F821,F822,F823 are the "showstopper" flake8 issues that can halt the runtime with a SyntaxError, NameError, etc. These 5 are different from most other flake8 issues which are merely "style violations" -- useful for readability but they do not effect runtime safety.

F821: undefined name name
F822: undefined name name in __all__
F823: local variable name referenced before assignment
E901: SyntaxError or IndentationError
E999: SyntaxError -- failed to compile a file into an Abstract Syntax Tree

I delete it.


Update HOSTING.md

seems the ci is breaking again...anyway i will fix it later

LGTM~

https://deno.com/blog/v1.14#changes-to-os-signals-apis, the ci is using deno 1.14 that have break change of Signal


Monster's IDs for the resources

Thank very much for your contribution, I hope we can make this repository very useful for everyone ❤


Napari >0.4.5 window non-responsive if created on non-primary display.

🐛 Bug
Starting from version 0.4.6 launching napari will result in white, unresponsive window, if created on secondary display.
This is certainly tied to the the ability to save window position, which was introduced in 0.4.6.
It could also be linked to the case of the secondary screen being in portrait orientation.
EDIT: Issue is identical, regardless of screen orientation
To Reproduce
Steps to reproduce the behavior:

Launch napari on primary screen
Move napari window to second (non-primary) display
Close napari window.
Launch napari
Napari launches a white, unresponsive window in the previous position on the secondary screen. Window needs to be terminated.

Steps to fix the behavior:

Close napari
Disable all non-primary displays
Launch napari
napari launches correctly on the primary screen.

Expected behavior
Napari should work as expected on systems with multiple displays.
Environment
napari: 0.4.7
Platform: Windows-10-10.0.19041-SP0
Python: 3.8.10 | packaged by conda-forge | (default, May 11 2021, 06:25:23) [MSC v.1916 64 bit (AMD64)]
Qt: 5.15.2
PyQt5: 5.15.4
NumPy: 1.20.3
SciPy: 1.6.3
Dask: 2021.05.0
VisPy: 0.6.6
OpenGL:
-GL version:  4.6.0 NVIDIA 462.31
-MAX_TEXTURE_SIZE: 32768
Screens:
-screen 1: resolution 2560x1440, scale 1.0
-screen 2: resolution 1440x2560, scale 1.0
Plugins:
-console: 0.0.3
-svg: 0.1.5
Warning logged
WARNING: QWindowsWindow::setGeometry: Unable to set geometry 1440x2537+2560-617 (frame: 1456x2576+2552-648) on QWidgetWindow/"_QtMainWindowClassWindow" on "\.\DISPLAY1". Resulting geometry: 1440x1421+2560-617 (frame: 1456x1460+2552-648) margins: 8, 31, 8, 8 minimum size: 488x519 MINMAXINFO maxSize=0,0 maxpos=0,0 mintrack=504,558 maxtrack=0,0)

Hi @Remote-Radical, thanks for the report.

it could also be linked to the case of the secondary screen being in portrait orientation.

Could you double check this option?
While I get my hands on an external monitor I will check using ipad/iphone and see if I can reproduce it.

it could also be linked to the case of the secondary screen being in portrait orientation.

Could you double check this option?

I have verified that the issue is identical regardless of display alignment and orientation.

I have verified that the issue is identical regardless of display alignment and orientation.

Thanks :-)

@Remote-Radical what version of Qt are you using?
I have not been able to reproduce this on OSX with the latest napari. @napari/core-devs could anyone please check if you can reproduce this, or if it a Windows specific Issue?

also unable to reproduce on master/4.10, environment info below

napari: 0.4.11.dev22+g955da0af
Platform: macOS-11.2.1-x86_64-i386-64bit
System: MacOS 11.2.1
Python: 3.9.5 | packaged by conda-forge | (default, Jun 19 2021, 00:27:35)  [Clang 11.1.0 ]
Qt: 5.15.2
PyQt5: 5.15.4
NumPy: 1.21.0
SciPy: 1.7.0
Dask: 2021.06.2
VisPy: 0.6.6

OpenGL:
  - GL version:  2.1 Metal - 71.0.7
  - MAX_TEXTURE_SIZE: 16384

Screens:
  - screen 1: resolution 1440x900, scale 2.0

Plugins:
  - console: 0.0.3
  - scikit-image: 0.4.11.dev22+g955da0af
  - svg: 0.1.5

I don't see the unresponsive window but I do see some warnings.
WARNING: QWindowsWindow::setGeometry: Unable to set geometry 2176x1366-2088+831 (frame: 2198x1422-2099+786) on QWidgetWindow/"_QtMainWindowClassWindow" on "\\.\DISPLAY2". Resulting geometry: 2611x1640-2086+838 (frame: 2633x1696-2097+793) margins: 11, 45, 11, 11 minimum size: 488x539 MINMAXINFO maxSize=0,0 maxpos=0,0 mintrack=998,1134 maxtrack=0,0)
17:03:05
WARNING QWindowsWindow::setGeometry: Unable to set geometry 2176x1366-2088+831 (frame: 2198x1422-2099+786) on QWidgetWindow/"_QtMainWindowClassWindow" on "\\.\DISPLAY2". Resulting geometry: 2611x1640-2086+838 (frame: 2633x1696-2097+793) margins: 11, 45, 11, 11 minimum size: 488x539 MINMAXINFO maxSize=0,0 maxpos=0,0 mintrack=998,1134 maxtrack=0,0)

I see the same behavior in the current master and in 0.4.7.  My info:
napari: 0.4.7
Platform: Windows-10-10.0.19043-SP0
Python: 3.8.10 (default, May 19 2021, 13:12:57) [MSC v.1916 64 bit (AMD64)]
Qt: 5.15.2
PyQt5: 5.15.4
NumPy: 1.21.0
SciPy: 1.7.0
Dask: 2021.06.2
VisPy: 0.7.0

OpenGL:
  - GL version:  4.6.0 NVIDIA 466.77
  - MAX_TEXTURE_SIZE: 32768

Screens:
  - screen 1: resolution 3840x2160, scale 1.0
  - screen 2: resolution 1800x3200, scale 1.0

Plugins:
  - console: 0.0.3
  - svg: 0.1.5

I should have mentioned, the warnings only show up when starting napari on the second display.

OMG 👋 👋 👋 @nclack!!! 😊 😊 😊
@Remote-Radical would you mind attempting to reproduce your issue on a more recent napari and/or another machine? It seems hard to reproduce and thus to fix...
Having said that @nclack given your setup maybe you could investigate the warnings and how one might be able to get rid of them? Fixing the warnings might fix the issue in other users' cases.

I encountered similar issue. I have a new laptop, the first time I install and use napari on this laptop is when the laptop connected to a secondary display at my office. After getting back home, where I don't have the secondary display, I cannot start napari anymore on the laptop, specifically the window does not show up and got the following message:
WARNING: QWindowsWindow::setGeometry: Unable to set geometry 1924x1214-6218+212 (frame: 1946x1270-6229+167) on QWidgetWindow/"_QtMainWindowClassWindow" on "\\.\DISPLAY1". Resulting geometry: 1924x1098-6218+212 (frame: 1946x1154-6229+167) margins: 11, 45, 11, 11 minimum size: 608x549 MINMAXINFO maxSize=0,0 maxpos=0,0 mintrack=1238,1154 maxtrack=0,0)
20:16:11 WARNING QWindowsWindow::setGeometry: Unable to set geometry 1924x1214-6218+212 (frame: 1946x1270-6229+167) on QWidgetWindow/"_QtMainWindowClassWindow" on "\\.\DISPLAY1". Resulting geometry: 1924x1098-6218+212 (frame: 1946x1154-6229+167) margins: 11, 45, 11, 11 minimum size: 608x549 MINMAXINFO maxSize=0,0 maxpos=0,0 mintrack=1238,1154 maxtrack=0,0)

Tried to re-install napari on a different conda environment, still not work.
napari verion = 0.4.12
Windows 10

@jxchen01 what OS are you working on?

@jxchen01 please note that until we fix this you can run napari --reset on the command line to clear the settings, including the screen position settings that are causing the problem.

@melonora You were playing with external monitors and napari windows, did you run into this? Is this bug still a thing?

From what I can tell this bug does not exist anymore. It was related to the window positions being outside the screen geometry in case of the secondary screen being disconnected. This was fixed with #5915. I will close this one.
There are some other issues, but for those I already opened other issues. I will therefore close this issue.