From 77f92f112277c6fd48e4d47a08515f1f4c8200ad Mon Sep 17 00:00:00 2001 From: "Miguel A. Cabrera Minagorri" Date: Mon, 11 Apr 2022 16:59:09 +0200 Subject: [PATCH] Reorganize common files and create fetch commmits script Signed-off-by: Miguel A. Cabrera Minagorri --- .../ISSUE_TEMPLATE/bug_report.yml | 0 .../ISSUE_TEMPLATE/config.yml | 0 .../ISSUE_TEMPLATE/feature_request.yml | 0 .../PULL_REQUEST_TEMPLATE.md | 0 .../.github => .github}/workflows/stale.yml | 0 .github/workflows/sync.yaml | 17 +++ README.md | 3 + bitnami/acmesolver/CODE_OF_CONDUCT.md | 17 --- bitnami/acmesolver/CONTRIBUTING.md | 52 -------- bitnami/acmesolver/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- bitnami/airflow-exporter/CODE_OF_CONDUCT.md | 17 --- bitnami/airflow-exporter/CONTRIBUTING.md | 52 -------- bitnami/airflow-exporter/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- bitnami/airflow-scheduler/CODE_OF_CONDUCT.md | 17 --- bitnami/airflow-scheduler/CONTRIBUTING.md | 52 -------- bitnami/airflow-scheduler/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- bitnami/airflow-worker/CODE_OF_CONDUCT.md | 17 --- bitnami/airflow-worker/CONTRIBUTING.md | 52 -------- bitnami/airflow-worker/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../airflow/.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../airflow/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/airflow/.github/workflows/stale.yml | 20 --- bitnami/airflow/CODE_OF_CONDUCT.md | 17 --- bitnami/airflow/CONTRIBUTING.md | 52 -------- bitnami/airflow/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../alertmanager/.github/workflows/stale.yml | 20 --- bitnami/alertmanager/CODE_OF_CONDUCT.md | 17 --- bitnami/alertmanager/CONTRIBUTING.md | 52 -------- bitnami/alertmanager/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- bitnami/apache-exporter/CODE_OF_CONDUCT.md | 17 --- bitnami/apache-exporter/CONTRIBUTING.md | 52 -------- bitnami/apache-exporter/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../apache/.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../apache/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/apache/.github/workflows/stale.yml | 20 --- bitnami/apache/CODE_OF_CONDUCT.md | 17 --- bitnami/apache/CONTRIBUTING.md | 52 -------- bitnami/apache/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../argo-cd/.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../argo-cd/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/argo-cd/.github/workflows/stale.yml | 20 --- bitnami/argo-cd/CODE_OF_CONDUCT.md | 17 --- bitnami/argo-cd/CONTRIBUTING.md | 52 -------- bitnami/argo-cd/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- bitnami/argo-workflow-cli/CODE_OF_CONDUCT.md | 17 --- bitnami/argo-workflow-cli/CONTRIBUTING.md | 52 -------- bitnami/argo-workflow-cli/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- .../CODE_OF_CONDUCT.md | 17 --- .../argo-workflow-controller/CONTRIBUTING.md | 52 -------- bitnami/argo-workflow-controller/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- bitnami/argo-workflow-exec/CODE_OF_CONDUCT.md | 17 --- bitnami/argo-workflow-exec/CONTRIBUTING.md | 52 -------- bitnami/argo-workflow-exec/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../aspnet-core/.github/workflows/stale.yml | 20 --- bitnami/aspnet-core/CODE_OF_CONDUCT.md | 17 --- bitnami/aspnet-core/CONTRIBUTING.md | 52 -------- bitnami/aspnet-core/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../aws-cli/.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../aws-cli/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/aws-cli/.github/workflows/stale.yml | 20 --- bitnami/aws-cli/CODE_OF_CONDUCT.md | 17 --- bitnami/aws-cli/CONTRIBUTING.md | 52 -------- bitnami/aws-cli/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/azure-cli/.github/workflows/stale.yml | 20 --- bitnami/azure-cli/CODE_OF_CONDUCT.md | 17 --- bitnami/azure-cli/CONTRIBUTING.md | 52 -------- bitnami/azure-cli/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../bitnami-shell/.github/workflows/stale.yml | 20 --- bitnami/bitnami-shell/CODE_OF_CONDUCT.md | 17 --- bitnami/bitnami-shell/CONTRIBUTING.md | 52 -------- bitnami/bitnami-shell/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- bitnami/blackbox-exporter/CODE_OF_CONDUCT.md | 17 --- bitnami/blackbox-exporter/CONTRIBUTING.md | 52 -------- bitnami/blackbox-exporter/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../cainjector/.github/workflows/stale.yml | 20 --- bitnami/cainjector/CODE_OF_CONDUCT.md | 17 --- bitnami/cainjector/CONTRIBUTING.md | 52 -------- bitnami/cainjector/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- bitnami/cassandra-exporter/CODE_OF_CONDUCT.md | 17 --- bitnami/cassandra-exporter/CONTRIBUTING.md | 52 -------- bitnami/cassandra-exporter/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/cassandra/.github/workflows/stale.yml | 20 --- bitnami/cassandra/CODE_OF_CONDUCT.md | 17 --- bitnami/cassandra/CONTRIBUTING.md | 52 -------- bitnami/cassandra/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- .../cert-manager-webhook/CODE_OF_CONDUCT.md | 17 --- bitnami/cert-manager-webhook/CONTRIBUTING.md | 52 -------- bitnami/cert-manager-webhook/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../cert-manager/.github/workflows/stale.yml | 20 --- bitnami/cert-manager/CODE_OF_CONDUCT.md | 17 --- bitnami/cert-manager/CONTRIBUTING.md | 52 -------- bitnami/cert-manager/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../chartmuseum/.github/workflows/stale.yml | 20 --- bitnami/chartmuseum/CODE_OF_CONDUCT.md | 17 --- bitnami/chartmuseum/CONTRIBUTING.md | 52 -------- bitnami/chartmuseum/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- bitnami/cluster-autoscaler/CODE_OF_CONDUCT.md | 17 --- bitnami/cluster-autoscaler/CONTRIBUTING.md | 52 -------- bitnami/cluster-autoscaler/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../codeigniter/.github/workflows/stale.yml | 20 --- bitnami/codeigniter/CODE_OF_CONDUCT.md | 17 --- bitnami/codeigniter/CONTRIBUTING.md | 52 -------- bitnami/codeigniter/LICENSE.md | 13 -- bitnami/concourse/.github/bug_report.yml | 41 ------ bitnami/concourse/.github/config.yml | 1 - bitnami/concourse/.github/feature_request.yml | 29 ----- bitnami/concourse/CONTRIBUTING.md | 52 -------- bitnami/concourse/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- bitnami/configmap-reload/CODE_OF_CONDUCT.md | 17 --- bitnami/configmap-reload/CONTRIBUTING.md | 52 -------- bitnami/configmap-reload/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- .../CODE_OF_CONDUCT.md | 17 --- .../configurable-http-proxy/CONTRIBUTING.md | 52 -------- bitnami/configurable-http-proxy/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- bitnami/consul-exporter/CODE_OF_CONDUCT.md | 17 --- bitnami/consul-exporter/CONTRIBUTING.md | 52 -------- bitnami/consul-exporter/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../consul/.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../consul/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/consul/.github/workflows/stale.yml | 20 --- bitnami/consul/CODE_OF_CONDUCT.md | 17 --- bitnami/consul/CONTRIBUTING.md | 52 -------- bitnami/consul/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- bitnami/contour-operator/CODE_OF_CONDUCT.md | 17 --- bitnami/contour-operator/CONTRIBUTING.md | 52 -------- bitnami/contour-operator/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../contour/.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../contour/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/contour/.github/workflows/stale.yml | 20 --- bitnami/contour/CODE_OF_CONDUCT.md | 17 --- bitnami/contour/CONTRIBUTING.md | 52 -------- bitnami/contour/LICENSE.md | 13 -- bitnami/cosign/.github/ISSUE_TEMPLATE.md | 21 ---- .../cosign/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/cosign/.github/workflows/stale.yml | 20 --- bitnami/cosign/CODE_OF_CONDUCT.md | 17 --- bitnami/cosign/CONTRIBUTING.md | 52 -------- bitnami/cosign/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../couchdb/.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../couchdb/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/couchdb/.github/workflows/stale.yml | 20 --- bitnami/couchdb/CODE_OF_CONDUCT.md | 17 --- bitnami/couchdb/CONTRIBUTING.md | 52 -------- bitnami/couchdb/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- .../dataplatform-emitter/CODE_OF_CONDUCT.md | 17 --- bitnami/dataplatform-emitter/CONTRIBUTING.md | 52 -------- bitnami/dataplatform-emitter/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- .../dataplatform-exporter/CODE_OF_CONDUCT.md | 17 --- bitnami/dataplatform-exporter/CONTRIBUTING.md | 52 -------- bitnami/dataplatform-exporter/LICENSE.md | 13 -- .../dex/.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ bitnami/dex/.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- bitnami/dex/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/dex/.github/workflows/stale.yml | 20 --- bitnami/dex/CODE_OF_CONDUCT.md | 17 --- bitnami/dex/CONTRIBUTING.md | 52 -------- bitnami/dex/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/discourse/.github/workflows/stale.yml | 20 --- bitnami/discourse/CODE_OF_CONDUCT.md | 17 --- bitnami/discourse/CONTRIBUTING.md | 52 -------- bitnami/discourse/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../dokuwiki/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/dokuwiki/.github/workflows/stale.yml | 20 --- bitnami/dokuwiki/CODE_OF_CONDUCT.md | 17 --- bitnami/dokuwiki/CONTRIBUTING.md | 52 -------- bitnami/dokuwiki/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../dotnet-sdk/.github/workflows/stale.yml | 20 --- bitnami/dotnet-sdk/CODE_OF_CONDUCT.md | 17 --- bitnami/dotnet-sdk/CONTRIBUTING.md | 52 -------- bitnami/dotnet-sdk/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../dotnet/.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../dotnet/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/dotnet/.github/workflows/stale.yml | 20 --- bitnami/dotnet/CODE_OF_CONDUCT.md | 17 --- bitnami/dotnet/CONTRIBUTING.md | 52 -------- bitnami/dotnet/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../dreamfactory/.github/workflows/stale.yml | 20 --- bitnami/dreamfactory/CODE_OF_CONDUCT.md | 17 --- bitnami/dreamfactory/CONTRIBUTING.md | 52 -------- bitnami/dreamfactory/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../drupal-nginx/.github/workflows/stale.yml | 20 --- bitnami/drupal-nginx/CODE_OF_CONDUCT.md | 17 --- bitnami/drupal-nginx/CONTRIBUTING.md | 52 -------- bitnami/drupal-nginx/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../drupal/.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../drupal/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/drupal/.github/workflows/stale.yml | 20 --- bitnami/drupal/CODE_OF_CONDUCT.md | 17 --- bitnami/drupal/CONTRIBUTING.md | 52 -------- bitnami/drupal/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../ejbca/.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../ejbca/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/ejbca/.github/workflows/stale.yml | 20 --- bitnami/ejbca/CODE_OF_CONDUCT.md | 17 --- bitnami/ejbca/CONTRIBUTING.md | 52 -------- bitnami/ejbca/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- .../elasticsearch-curator/CODE_OF_CONDUCT.md | 17 --- bitnami/elasticsearch-curator/CONTRIBUTING.md | 52 -------- bitnami/elasticsearch-curator/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- .../elasticsearch-exporter/CODE_OF_CONDUCT.md | 17 --- .../elasticsearch-exporter/CONTRIBUTING.md | 52 -------- bitnami/elasticsearch-exporter/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../elasticsearch/.github/workflows/stale.yml | 20 --- bitnami/elasticsearch/CODE_OF_CONDUCT.md | 17 --- bitnami/elasticsearch/CONTRIBUTING.md | 52 -------- bitnami/elasticsearch/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../envoy/.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../envoy/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/envoy/.github/workflows/stale.yml | 20 --- bitnami/envoy/CODE_OF_CONDUCT.md | 17 --- bitnami/envoy/CONTRIBUTING.md | 52 -------- bitnami/envoy/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../etcd/.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- bitnami/etcd/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/etcd/.github/workflows/stale.yml | 20 --- bitnami/etcd/CODE_OF_CONDUCT.md | 17 --- bitnami/etcd/CONTRIBUTING.md | 52 -------- bitnami/etcd/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../express/.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../express/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/express/.github/workflows/stale.yml | 20 --- bitnami/express/CODE_OF_CONDUCT.md | 17 --- bitnami/express/CONTRIBUTING.md | 52 -------- bitnami/express/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../external-dns/.github/workflows/stale.yml | 20 --- bitnami/external-dns/CODE_OF_CONDUCT.md | 17 --- bitnami/external-dns/CONTRIBUTING.md | 52 -------- bitnami/external-dns/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../fluent-bit/.github/workflows/stale.yml | 20 --- bitnami/fluent-bit/CODE_OF_CONDUCT.md | 17 --- bitnami/fluent-bit/CONTRIBUTING.md | 52 -------- bitnami/fluent-bit/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- bitnami/fluentd-exporter/CODE_OF_CONDUCT.md | 17 --- bitnami/fluentd-exporter/CONTRIBUTING.md | 52 -------- bitnami/fluentd-exporter/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../fluentd/.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../fluentd/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/fluentd/.github/workflows/stale.yml | 20 --- bitnami/fluentd/CODE_OF_CONDUCT.md | 17 --- bitnami/fluentd/CONTRIBUTING.md | 52 -------- bitnami/fluentd/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../geode/.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../geode/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/geode/.github/stale.yml | 36 ------ bitnami/geode/.github/workflows/stale.yml | 20 --- bitnami/geode/CODE_OF_CONDUCT.md | 17 --- bitnami/geode/CONTRIBUTING.md | 52 -------- bitnami/geode/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../ghost/.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../ghost/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/ghost/.github/workflows/stale.yml | 20 --- bitnami/ghost/CODE_OF_CONDUCT.md | 17 --- bitnami/ghost/CONTRIBUTING.md | 52 -------- bitnami/ghost/LICENSE.md | 13 -- .../git/.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ bitnami/git/.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- bitnami/git/.github/PULL_REQUEST_TEMPLATE.md | 33 ----- bitnami/git/.github/workflows/stale.yml | 20 --- bitnami/git/CODE_OF_CONDUCT.md | 17 --- bitnami/git/CONTRIBUTING.md | 52 -------- bitnami/git/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- .../gitlab-runner-helper/CODE_OF_CONDUCT.md | 17 --- bitnami/gitlab-runner-helper/CONTRIBUTING.md | 52 -------- bitnami/gitlab-runner-helper/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../gitlab-runner/.github/workflows/stale.yml | 20 --- bitnami/gitlab-runner/CODE_OF_CONDUCT.md | 17 --- bitnami/gitlab-runner/CONTRIBUTING.md | 52 -------- bitnami/gitlab-runner/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../golang/.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../golang/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/golang/.github/workflows/stale.yml | 20 --- bitnami/golang/CODE_OF_CONDUCT.md | 17 --- bitnami/golang/CONTRIBUTING.md | 52 -------- bitnami/golang/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- bitnami/google-cloud-sdk/CODE_OF_CONDUCT.md | 17 --- bitnami/google-cloud-sdk/CONTRIBUTING.md | 52 -------- bitnami/google-cloud-sdk/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../gradle/.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../gradle/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/gradle/.github/workflows/stale.yml | 20 --- bitnami/gradle/CODE_OF_CONDUCT.md | 17 --- bitnami/gradle/CONTRIBUTING.md | 52 -------- bitnami/gradle/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- .../grafana-image-renderer/CODE_OF_CONDUCT.md | 17 --- .../grafana-image-renderer/CONTRIBUTING.md | 52 -------- bitnami/grafana-image-renderer/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- bitnami/grafana-operator/CODE_OF_CONDUCT.md | 17 --- bitnami/grafana-operator/CONTRIBUTING.md | 52 -------- bitnami/grafana-operator/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- .../grafana-tempo-query/CODE_OF_CONDUCT.md | 17 --- bitnami/grafana-tempo-query/CONTRIBUTING.md | 52 -------- bitnami/grafana-tempo-query/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- .../grafana-tempo-vulture/CODE_OF_CONDUCT.md | 17 --- bitnami/grafana-tempo-vulture/CONTRIBUTING.md | 52 -------- bitnami/grafana-tempo-vulture/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../grafana-tempo/.github/workflows/stale.yml | 20 --- bitnami/grafana-tempo/CODE_OF_CONDUCT.md | 17 --- bitnami/grafana-tempo/CONTRIBUTING.md | 52 -------- bitnami/grafana-tempo/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../grafana/.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../grafana/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/grafana/.github/workflows/stale.yml | 20 --- bitnami/grafana/CODE_OF_CONDUCT.md | 17 --- bitnami/grafana/CONTRIBUTING.md | 52 -------- bitnami/grafana/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../haproxy/.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../haproxy/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/haproxy/.github/workflows/stale.yml | 20 --- bitnami/haproxy/CODE_OF_CONDUCT.md | 17 --- bitnami/haproxy/CONTRIBUTING.md | 52 -------- bitnami/haproxy/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- .../harbor-adapter-clair/CODE_OF_CONDUCT.md | 17 --- bitnami/harbor-adapter-clair/CONTRIBUTING.md | 52 -------- bitnami/harbor-adapter-clair/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- .../harbor-adapter-trivy/CODE_OF_CONDUCT.md | 17 --- bitnami/harbor-adapter-trivy/CONTRIBUTING.md | 52 -------- bitnami/harbor-adapter-trivy/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../harbor-clair/.github/workflows/stale.yml | 20 --- bitnami/harbor-clair/CODE_OF_CONDUCT.md | 17 --- bitnami/harbor-clair/CONTRIBUTING.md | 52 -------- bitnami/harbor-clair/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../harbor-core/.github/workflows/stale.yml | 20 --- bitnami/harbor-core/CODE_OF_CONDUCT.md | 17 --- bitnami/harbor-core/CONTRIBUTING.md | 52 -------- bitnami/harbor-core/LICENSE.md | 13 -- .../harbor-exporter/.github/ISSUE_TEMPLATE.md | 21 ---- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- bitnami/harbor-exporter/CODE_OF_CONDUCT.md | 17 --- bitnami/harbor-exporter/CONTRIBUTING.md | 52 -------- bitnami/harbor-exporter/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- bitnami/harbor-jobservice/CODE_OF_CONDUCT.md | 17 --- bitnami/harbor-jobservice/CONTRIBUTING.md | 52 -------- bitnami/harbor-jobservice/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- .../harbor-notary-server/CODE_OF_CONDUCT.md | 17 --- bitnami/harbor-notary-server/CONTRIBUTING.md | 52 -------- bitnami/harbor-notary-server/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- .../harbor-notary-signer/CODE_OF_CONDUCT.md | 17 --- bitnami/harbor-notary-signer/CONTRIBUTING.md | 52 -------- bitnami/harbor-notary-signer/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../harbor-portal/.github/workflows/stale.yml | 20 --- bitnami/harbor-portal/CODE_OF_CONDUCT.md | 17 --- bitnami/harbor-portal/CONTRIBUTING.md | 52 -------- bitnami/harbor-portal/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- bitnami/harbor-registry/CODE_OF_CONDUCT.md | 17 --- bitnami/harbor-registry/CONTRIBUTING.md | 52 -------- bitnami/harbor-registry/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- bitnami/harbor-registryctl/CODE_OF_CONDUCT.md | 17 --- bitnami/harbor-registryctl/CONTRIBUTING.md | 52 -------- bitnami/harbor-registryctl/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- bitnami/influxdb-relay/CODE_OF_CONDUCT.md | 17 --- bitnami/influxdb-relay/CONTRIBUTING.md | 52 -------- bitnami/influxdb-relay/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../influxdb/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/influxdb/.github/workflows/stale.yml | 20 --- bitnami/influxdb/CODE_OF_CONDUCT.md | 17 --- bitnami/influxdb/CONTRIBUTING.md | 52 -------- bitnami/influxdb/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../jasperreports/.github/workflows/stale.yml | 20 --- bitnami/jasperreports/CODE_OF_CONDUCT.md | 17 --- bitnami/jasperreports/CONTRIBUTING.md | 52 -------- bitnami/jasperreports/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../java/.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- bitnami/java/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/java/.github/workflows/stale.yml | 20 --- bitnami/java/CODE_OF_CONDUCT.md | 17 --- bitnami/java/CONTRIBUTING.md | 52 -------- bitnami/java/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- bitnami/jenkins-exporter/CODE_OF_CONDUCT.md | 17 --- bitnami/jenkins-exporter/CONTRIBUTING.md | 52 -------- bitnami/jenkins-exporter/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../jenkins/.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../jenkins/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/jenkins/.github/workflows/stale.yml | 20 --- bitnami/jenkins/CODE_OF_CONDUCT.md | 17 --- bitnami/jenkins/CONTRIBUTING.md | 52 -------- bitnami/jenkins/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../jmx-exporter/.github/workflows/stale.yml | 20 --- bitnami/jmx-exporter/CODE_OF_CONDUCT.md | 17 --- bitnami/jmx-exporter/CONTRIBUTING.md | 52 -------- bitnami/jmx-exporter/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../joomla/.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../joomla/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/joomla/.github/workflows/stale.yml | 20 --- bitnami/joomla/CODE_OF_CONDUCT.md | 17 --- bitnami/joomla/CONTRIBUTING.md | 52 -------- bitnami/joomla/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../jruby/.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../jruby/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/jruby/.github/workflows/stale.yml | 20 --- bitnami/jruby/CODE_OF_CONDUCT.md | 17 --- bitnami/jruby/CONTRIBUTING.md | 52 -------- bitnami/jruby/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../jsonnet/.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../jsonnet/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/jsonnet/.github/workflows/stale.yml | 20 --- bitnami/jsonnet/CODE_OF_CONDUCT.md | 17 --- bitnami/jsonnet/CONTRIBUTING.md | 52 -------- bitnami/jsonnet/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- .../jupyter-base-notebook/CODE_OF_CONDUCT.md | 17 --- bitnami/jupyter-base-notebook/CONTRIBUTING.md | 52 -------- bitnami/jupyter-base-notebook/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../jupyterhub/.github/workflows/stale.yml | 20 --- bitnami/jupyterhub/CODE_OF_CONDUCT.md | 17 --- bitnami/jupyterhub/CONTRIBUTING.md | 52 -------- bitnami/jupyterhub/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- bitnami/kafka-exporter/CODE_OF_CONDUCT.md | 17 --- bitnami/kafka-exporter/CONTRIBUTING.md | 52 -------- bitnami/kafka-exporter/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../kafka/.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../kafka/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/kafka/.github/workflows/stale.yml | 20 --- bitnami/kafka/CODE_OF_CONDUCT.md | 17 --- bitnami/kafka/CONTRIBUTING.md | 52 -------- bitnami/kafka/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/kapacitor/.github/workflows/stale.yml | 20 --- bitnami/kapacitor/CODE_OF_CONDUCT.md | 17 --- bitnami/kapacitor/CONTRIBUTING.md | 52 -------- bitnami/kapacitor/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- .../keycloak-config-cli/CODE_OF_CONDUCT.md | 17 --- bitnami/keycloak-config-cli/CONTRIBUTING.md | 52 -------- bitnami/keycloak-config-cli/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE.md | 22 ---- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- .../keycloak-gatekeeper/CODE_OF_CONDUCT.md | 17 --- bitnami/keycloak-gatekeeper/CONTRIBUTING.md | 52 -------- bitnami/keycloak-gatekeeper/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../keycloak/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/keycloak/.github/workflows/stale.yml | 20 --- bitnami/keycloak/CODE_OF_CONDUCT.md | 17 --- bitnami/keycloak/CONTRIBUTING.md | 52 -------- bitnami/keycloak/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../kiam/.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- bitnami/kiam/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/kiam/.github/workflows/stale.yml | 20 --- bitnami/kiam/CODE_OF_CONDUCT.md | 17 --- bitnami/kiam/CONTRIBUTING.md | 52 -------- bitnami/kiam/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../kibana/.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../kibana/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/kibana/.github/workflows/stale.yml | 20 --- bitnami/kibana/CODE_OF_CONDUCT.md | 17 --- bitnami/kibana/CONTRIBUTING.md | 52 -------- bitnami/kibana/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- .../CODE_OF_CONDUCT.md | 17 --- .../kong-ingress-controller/CONTRIBUTING.md | 52 -------- bitnami/kong-ingress-controller/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../kong/.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- bitnami/kong/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/kong/.github/workflows/stale.yml | 20 --- bitnami/kong/CODE_OF_CONDUCT.md | 17 --- bitnami/kong/CONTRIBUTING.md | 52 -------- bitnami/kong/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- bitnami/kube-rbac-proxy/CODE_OF_CONDUCT.md | 17 --- bitnami/kube-rbac-proxy/CONTRIBUTING.md | 52 -------- bitnami/kube-rbac-proxy/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- bitnami/kube-state-metrics/CODE_OF_CONDUCT.md | 17 --- bitnami/kube-state-metrics/CONTRIBUTING.md | 52 -------- bitnami/kube-state-metrics/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../kubeapps-apis/.github/workflows/stale.yml | 20 --- bitnami/kubeapps-apis/CODE_OF_CONDUCT.md | 17 --- bitnami/kubeapps-apis/CONTRIBUTING.md | 52 -------- bitnami/kubeapps-apis/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- .../CODE_OF_CONDUCT.md | 17 --- .../CONTRIBUTING.md | 52 -------- .../LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- .../kubeapps-asset-syncer/CODE_OF_CONDUCT.md | 17 --- bitnami/kubeapps-asset-syncer/CONTRIBUTING.md | 52 -------- bitnami/kubeapps-asset-syncer/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- bitnami/kubeapps-assetsvc/CODE_OF_CONDUCT.md | 17 --- bitnami/kubeapps-assetsvc/CONTRIBUTING.md | 52 -------- bitnami/kubeapps-assetsvc/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- bitnami/kubeapps-dashboard/CODE_OF_CONDUCT.md | 17 --- bitnami/kubeapps-dashboard/CONTRIBUTING.md | 52 -------- bitnami/kubeapps-dashboard/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- bitnami/kubeapps-kubeops/CODE_OF_CONDUCT.md | 17 --- bitnami/kubeapps-kubeops/CONTRIBUTING.md | 52 -------- bitnami/kubeapps-kubeops/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- .../CODE_OF_CONDUCT.md | 17 --- .../kubeapps-pinniped-proxy/CONTRIBUTING.md | 52 -------- bitnami/kubeapps-pinniped-proxy/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../kubectl/.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../kubectl/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/kubectl/.github/workflows/stale.yml | 20 --- bitnami/kubectl/CODE_OF_CONDUCT.md | 17 --- bitnami/kubectl/CONTRIBUTING.md | 52 -------- bitnami/kubectl/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- .../CODE_OF_CONDUCT.md | 17 --- .../kubernetes-event-exporter/CONTRIBUTING.md | 52 -------- bitnami/kubernetes-event-exporter/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/kubewatch/.github/workflows/stale.yml | 20 --- bitnami/kubewatch/CODE_OF_CONDUCT.md | 17 --- bitnami/kubewatch/CONTRIBUTING.md | 52 -------- bitnami/kubewatch/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../laravel/.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../laravel/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/laravel/.github/workflows/stale.yml | 20 --- bitnami/laravel/CODE_OF_CONDUCT.md | 17 --- bitnami/laravel/CONTRIBUTING.md | 52 -------- bitnami/laravel/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- bitnami/logstash-exporter/CODE_OF_CONDUCT.md | 17 --- bitnami/logstash-exporter/CONTRIBUTING.md | 52 -------- bitnami/logstash-exporter/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../logstash/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/logstash/.github/workflows/stale.yml | 20 --- bitnami/logstash/CODE_OF_CONDUCT.md | 17 --- bitnami/logstash/CONTRIBUTING.md | 52 -------- bitnami/logstash/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../magento/.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../magento/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/magento/.github/workflows/stale.yml | 20 --- bitnami/magento/CODE_OF_CONDUCT.md | 17 --- bitnami/magento/CONTRIBUTING.md | 52 -------- bitnami/magento/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- bitnami/mariadb-galera/CODE_OF_CONDUCT.md | 17 --- bitnami/mariadb-galera/CONTRIBUTING.md | 52 -------- bitnami/mariadb-galera/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../mariadb/.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../mariadb/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/mariadb/.github/workflows/stale.yml | 20 --- bitnami/mariadb/CODE_OF_CONDUCT.md | 17 --- bitnami/mariadb/CONTRIBUTING.md | 52 -------- bitnami/mariadb/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../matomo/.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../matomo/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/matomo/.github/workflows/stale.yml | 20 --- bitnami/matomo/CODE_OF_CONDUCT.md | 17 --- bitnami/matomo/CONTRIBUTING.md | 52 -------- bitnami/matomo/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/mediawiki/.github/workflows/stale.yml | 20 --- bitnami/mediawiki/CODE_OF_CONDUCT.md | 17 --- bitnami/mediawiki/CONTRIBUTING.md | 52 -------- bitnami/mediawiki/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- bitnami/memcached-exporter/CODE_OF_CONDUCT.md | 17 --- bitnami/memcached-exporter/CONTRIBUTING.md | 52 -------- bitnami/memcached-exporter/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/memcached/.github/workflows/stale.yml | 20 --- bitnami/memcached/CODE_OF_CONDUCT.md | 17 --- bitnami/memcached/CONTRIBUTING.md | 52 -------- bitnami/memcached/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- bitnami/metallb-controller/CODE_OF_CONDUCT.md | 17 --- bitnami/metallb-controller/CONTRIBUTING.md | 52 -------- bitnami/metallb-controller/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- bitnami/metallb-speaker/CODE_OF_CONDUCT.md | 17 --- bitnami/metallb-speaker/CONTRIBUTING.md | 52 -------- bitnami/metallb-speaker/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- bitnami/metrics-server/CODE_OF_CONDUCT.md | 17 --- bitnami/metrics-server/CONTRIBUTING.md | 52 -------- bitnami/metrics-server/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../minio-client/.github/workflows/stale.yml | 20 --- bitnami/minio-client/CODE_OF_CONDUCT.md | 17 --- bitnami/minio-client/CONTRIBUTING.md | 52 -------- bitnami/minio-client/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../minio/.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../minio/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/minio/.github/workflows/stale.yml | 20 --- bitnami/minio/CODE_OF_CONDUCT.md | 17 --- bitnami/minio/CONTRIBUTING.md | 52 -------- bitnami/minio/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- bitnami/mongodb-exporter/CODE_OF_CONDUCT.md | 17 --- bitnami/mongodb-exporter/CONTRIBUTING.md | 52 -------- bitnami/mongodb-exporter/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- bitnami/mongodb-sharded/CODE_OF_CONDUCT.md | 17 --- bitnami/mongodb-sharded/CONTRIBUTING.md | 52 -------- bitnami/mongodb-sharded/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../mongodb/.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../mongodb/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/mongodb/.github/workflows/stale.yml | 20 --- bitnami/mongodb/CODE_OF_CONDUCT.md | 17 --- bitnami/mongodb/CONTRIBUTING.md | 52 -------- bitnami/mongodb/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../moodle/.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../moodle/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/moodle/.github/workflows/stale.yml | 20 --- bitnami/moodle/CODE_OF_CONDUCT.md | 17 --- bitnami/moodle/CONTRIBUTING.md | 52 -------- bitnami/moodle/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../mxnet/.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../mxnet/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/mxnet/.github/workflows/stale.yml | 20 --- bitnami/mxnet/CODE_OF_CONDUCT.md | 17 --- bitnami/mxnet/CONTRIBUTING.md | 52 -------- bitnami/mxnet/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../mysql/.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../mysql/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/mysql/.github/workflows/stale.yml | 20 --- bitnami/mysql/CODE_OF_CONDUCT.md | 17 --- bitnami/mysql/CONTRIBUTING.md | 52 -------- bitnami/mysql/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- bitnami/mysqld-exporter/CODE_OF_CONDUCT.md | 17 --- bitnami/mysqld-exporter/CONTRIBUTING.md | 52 -------- bitnami/mysqld-exporter/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../nats-exporter/.github/workflows/stale.yml | 20 --- bitnami/nats-exporter/CODE_OF_CONDUCT.md | 17 --- bitnami/nats-exporter/CONTRIBUTING.md | 52 -------- bitnami/nats-exporter/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../nats/.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- bitnami/nats/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/nats/.github/workflows/stale.yml | 20 --- bitnami/nats/CODE_OF_CONDUCT.md | 17 --- bitnami/nats/CONTRIBUTING.md | 52 -------- bitnami/nats/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../neo4j/.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../neo4j/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/neo4j/.github/workflows/stale.yml | 20 --- bitnami/neo4j/CODE_OF_CONDUCT.md | 17 --- bitnami/neo4j/CONTRIBUTING.md | 52 -------- bitnami/neo4j/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- bitnami/nginx-exporter/CODE_OF_CONDUCT.md | 17 --- bitnami/nginx-exporter/CONTRIBUTING.md | 52 -------- bitnami/nginx-exporter/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- .../CODE_OF_CONDUCT.md | 17 --- .../nginx-ingress-controller/CONTRIBUTING.md | 52 -------- bitnami/nginx-ingress-controller/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../nginx-intel/.github/workflows/stale.yml | 20 --- bitnami/nginx-intel/CODE_OF_CONDUCT.md | 17 --- bitnami/nginx-intel/CONTRIBUTING.md | 52 -------- bitnami/nginx-intel/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- .../nginx-ldap-auth-daemon/CODE_OF_CONDUCT.md | 17 --- .../nginx-ldap-auth-daemon/CONTRIBUTING.md | 52 -------- bitnami/nginx-ldap-auth-daemon/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../nginx/.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../nginx/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/nginx/.github/workflows/stale.yml | 20 --- bitnami/nginx/CODE_OF_CONDUCT.md | 17 --- bitnami/nginx/CONTRIBUTING.md | 52 -------- bitnami/nginx/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../node-exporter/.github/workflows/stale.yml | 20 --- bitnami/node-exporter/CODE_OF_CONDUCT.md | 17 --- bitnami/node-exporter/CONTRIBUTING.md | 52 -------- bitnami/node-exporter/LICENSE.md | 13 -- .../node-snapshot/.github/ISSUE_TEMPLATE.md | 22 ---- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../node-snapshot/.github/workflows/stale.yml | 20 --- bitnami/node-snapshot/CODE_OF_CONDUCT.md | 17 --- bitnami/node-snapshot/CONTRIBUTING.md | 52 -------- bitnami/node-snapshot/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../node/.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- bitnami/node/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/node/.github/workflows/stale.yml | 20 --- bitnami/node/CODE_OF_CONDUCT.md | 17 --- bitnami/node/CONTRIBUTING.md | 52 -------- bitnami/node/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../oauth2-proxy/.github/workflows/stale.yml | 20 --- bitnami/oauth2-proxy/CODE_OF_CONDUCT.md | 17 --- bitnami/oauth2-proxy/CONTRIBUTING.md | 52 -------- bitnami/oauth2-proxy/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../odoo/.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- bitnami/odoo/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/odoo/.github/workflows/stale.yml | 20 --- bitnami/odoo/CODE_OF_CONDUCT.md | 17 --- bitnami/odoo/CONTRIBUTING.md | 52 -------- bitnami/odoo/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE.md | 22 ---- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- .../CODE_OF_CONDUCT.md | 17 --- .../open-service-broker-azure/CONTRIBUTING.md | 52 -------- bitnami/open-service-broker-azure/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../opencart/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/opencart/.github/workflows/stale.yml | 20 --- bitnami/opencart/CODE_OF_CONDUCT.md | 17 --- bitnami/opencart/CONTRIBUTING.md | 52 -------- bitnami/opencart/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../openldap/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/openldap/.github/workflows/stale.yml | 20 --- bitnami/openldap/CODE_OF_CONDUCT.md | 17 --- bitnami/openldap/CONTRIBUTING.md | 52 -------- bitnami/openldap/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/openresty/.github/workflows/stale.yml | 20 --- bitnami/openresty/CODE_OF_CONDUCT.md | 17 --- bitnami/openresty/CONTRIBUTING.md | 52 -------- bitnami/openresty/LICENSE.md | 13 -- bitnami/orangehrm/.github/ISSUE_TEMPLATE.md | 22 ---- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/orangehrm/.github/workflows/stale.yml | 20 --- bitnami/orangehrm/CODE_OF_CONDUCT.md | 17 --- bitnami/orangehrm/CONTRIBUTING.md | 52 -------- bitnami/orangehrm/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../oras/.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- bitnami/oras/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/oras/.github/workflows/stale.yml | 20 --- bitnami/oras/CODE_OF_CONDUCT.md | 17 --- bitnami/oras/CONTRIBUTING.md | 52 -------- bitnami/oras/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../osclass/.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../osclass/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/osclass/.github/workflows/stale.yml | 20 --- bitnami/osclass/CODE_OF_CONDUCT.md | 17 --- bitnami/osclass/CONTRIBUTING.md | 52 -------- bitnami/osclass/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../owncloud/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/owncloud/.github/workflows/stale.yml | 20 --- bitnami/owncloud/CODE_OF_CONDUCT.md | 17 --- bitnami/owncloud/CONTRIBUTING.md | 52 -------- bitnami/owncloud/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- bitnami/parse-dashboard/CODE_OF_CONDUCT.md | 17 --- bitnami/parse-dashboard/CONTRIBUTING.md | 52 -------- bitnami/parse-dashboard/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../parse/.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../parse/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/parse/.github/workflows/stale.yml | 20 --- bitnami/parse/CODE_OF_CONDUCT.md | 17 --- bitnami/parse/CONTRIBUTING.md | 52 -------- bitnami/parse/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- bitnami/percona-xtrabackup/CODE_OF_CONDUCT.md | 17 --- bitnami/percona-xtrabackup/CONTRIBUTING.md | 52 -------- bitnami/percona-xtrabackup/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/pgbouncer/.github/workflows/stale.yml | 20 --- bitnami/pgbouncer/CODE_OF_CONDUCT.md | 17 --- bitnami/pgbouncer/CONTRIBUTING.md | 52 -------- bitnami/pgbouncer/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../pgpool/.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../pgpool/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/pgpool/.github/workflows/stale.yml | 20 --- bitnami/pgpool/CODE_OF_CONDUCT.md | 17 --- bitnami/pgpool/CONTRIBUTING.md | 52 -------- bitnami/pgpool/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../php-fpm/.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../php-fpm/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/php-fpm/.github/workflows/stale.yml | 20 --- bitnami/php-fpm/CODE_OF_CONDUCT.md | 17 --- bitnami/php-fpm/CONTRIBUTING.md | 52 -------- bitnami/php-fpm/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../phpbb/.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../phpbb/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/phpbb/.github/workflows/stale.yml | 20 --- bitnami/phpbb/CODE_OF_CONDUCT.md | 17 --- bitnami/phpbb/CONTRIBUTING.md | 52 -------- bitnami/phpbb/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../phpmyadmin/.github/workflows/stale.yml | 20 --- bitnami/phpmyadmin/CODE_OF_CONDUCT.md | 17 --- bitnami/phpmyadmin/CONTRIBUTING.md | 52 -------- bitnami/phpmyadmin/LICENSE.md | 13 -- bitnami/phppgadmin/.github/ISSUE_TEMPLATE.md | 22 ---- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../phppgadmin/.github/workflows/stale.yml | 20 --- bitnami/phppgadmin/CODE_OF_CONDUCT.md | 17 --- bitnami/phppgadmin/CONTRIBUTING.md | 52 -------- bitnami/phppgadmin/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- bitnami/postgres-exporter/CODE_OF_CONDUCT.md | 17 --- bitnami/postgres-exporter/CONTRIBUTING.md | 52 -------- bitnami/postgres-exporter/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- bitnami/postgresql-repmgr/CODE_OF_CONDUCT.md | 17 --- bitnami/postgresql-repmgr/CONTRIBUTING.md | 52 -------- bitnami/postgresql-repmgr/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../postgresql/.github/workflows/stale.yml | 20 --- bitnami/postgresql/CODE_OF_CONDUCT.md | 17 --- bitnami/postgresql/CONTRIBUTING.md | 52 -------- bitnami/postgresql/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../prestashop/.github/workflows/stale.yml | 20 --- bitnami/prestashop/CODE_OF_CONDUCT.md | 17 --- bitnami/prestashop/CONTRIBUTING.md | 52 -------- bitnami/prestashop/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- .../prometheus-operator/CODE_OF_CONDUCT.md | 17 --- bitnami/prometheus-operator/CONTRIBUTING.md | 52 -------- bitnami/prometheus-operator/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- .../CODE_OF_CONDUCT.md | 17 --- .../prometheus-rsocket-proxy/CONTRIBUTING.md | 52 -------- bitnami/prometheus-rsocket-proxy/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../prometheus/.github/workflows/stale.yml | 20 --- bitnami/prometheus/CODE_OF_CONDUCT.md | 17 --- bitnami/prometheus/CONTRIBUTING.md | 52 -------- bitnami/prometheus/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../pushgateway/.github/workflows/stale.yml | 20 --- bitnami/pushgateway/CODE_OF_CONDUCT.md | 17 --- bitnami/pushgateway/CONTRIBUTING.md | 52 -------- bitnami/pushgateway/LICENSE.md | 13 -- .../python-snapshot/.github/ISSUE_TEMPLATE.md | 22 ---- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- bitnami/python-snapshot/CODE_OF_CONDUCT.md | 17 --- bitnami/python-snapshot/CONTRIBUTING.md | 52 -------- bitnami/python-snapshot/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../python/.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../python/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/python/.github/workflows/stale.yml | 20 --- bitnami/python/CODE_OF_CONDUCT.md | 17 --- bitnami/python/CONTRIBUTING.md | 52 -------- bitnami/python/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../pytorch/.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../pytorch/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/pytorch/.github/workflows/stale.yml | 20 --- bitnami/pytorch/CODE_OF_CONDUCT.md | 17 --- bitnami/pytorch/CONTRIBUTING.md | 52 -------- bitnami/pytorch/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- .../CODE_OF_CONDUCT.md | 17 --- .../rabbitmq-cluster-operator/CONTRIBUTING.md | 52 -------- bitnami/rabbitmq-cluster-operator/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../rabbitmq/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/rabbitmq/.github/workflows/stale.yml | 20 --- bitnami/rabbitmq/CODE_OF_CONDUCT.md | 17 --- bitnami/rabbitmq/CONTRIBUTING.md | 52 -------- bitnami/rabbitmq/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../rails/.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../rails/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/rails/.github/workflows/stale.yml | 20 --- bitnami/rails/CODE_OF_CONDUCT.md | 17 --- bitnami/rails/CONTRIBUTING.md | 52 -------- bitnami/rails/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../rclone/.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../rclone/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/rclone/.github/workflows/stale.yml | 20 --- bitnami/rclone/CODE_OF_CONDUCT.md | 17 --- bitnami/rclone/CONTRIBUTING.md | 52 -------- bitnami/rclone/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../redis-cluster/.github/workflows/stale.yml | 20 --- bitnami/redis-cluster/CODE_OF_CONDUCT.md | 17 --- bitnami/redis-cluster/CONTRIBUTING.md | 52 -------- bitnami/redis-cluster/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- bitnami/redis-exporter/CODE_OF_CONDUCT.md | 17 --- bitnami/redis-exporter/CONTRIBUTING.md | 52 -------- bitnami/redis-exporter/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- bitnami/redis-sentinel/CODE_OF_CONDUCT.md | 17 --- bitnami/redis-sentinel/CONTRIBUTING.md | 52 -------- bitnami/redis-sentinel/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../redis/.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../redis/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/redis/.github/workflows/stale.yml | 20 --- bitnami/redis/CODE_OF_CONDUCT.md | 17 --- bitnami/redis/CONTRIBUTING.md | 52 -------- bitnami/redis/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../redmine/.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../redmine/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/redmine/.github/workflows/stale.yml | 20 --- bitnami/redmine/CODE_OF_CONDUCT.md | 17 --- bitnami/redmine/CONTRIBUTING.md | 52 -------- bitnami/redmine/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../reportserver/.github/workflows/stale.yml | 20 --- bitnami/reportserver/CODE_OF_CONDUCT.md | 17 --- bitnami/reportserver/CONTRIBUTING.md | 52 -------- bitnami/reportserver/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- .../reportserverenterprise/CODE_OF_CONDUCT.md | 17 --- .../reportserverenterprise/CONTRIBUTING.md | 52 -------- bitnami/reportserverenterprise/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- .../CODE_OF_CONDUCT.md | 17 --- .../CONTRIBUTING.md | 52 -------- .../rmq-default-credential-updater/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- .../CODE_OF_CONDUCT.md | 17 --- .../CONTRIBUTING.md | 52 -------- .../LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../ruby/.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- bitnami/ruby/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/ruby/.github/workflows/stale.yml | 20 --- bitnami/ruby/CODE_OF_CONDUCT.md | 17 --- bitnami/ruby/CONTRIBUTING.md | 52 -------- bitnami/ruby/LICENSE.md | 13 -- .../service-catalog/.github/ISSUE_TEMPLATE.md | 22 ---- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- bitnami/service-catalog/CODE_OF_CONDUCT.md | 17 --- bitnami/service-catalog/CONTRIBUTING.md | 52 -------- bitnami/service-catalog/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../solr/.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- bitnami/solr/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/solr/.github/workflows/stale.yml | 20 --- bitnami/solr/CODE_OF_CONDUCT.md | 17 --- bitnami/solr/CONTRIBUTING.md | 52 -------- bitnami/solr/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/sonarqube/.github/workflows/stale.yml | 20 --- bitnami/sonarqube/CODE_OF_CONDUCT.md | 17 --- bitnami/sonarqube/CONTRIBUTING.md | 52 -------- bitnami/sonarqube/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../spark/.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../spark/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/spark/.github/workflows/stale.yml | 20 --- bitnami/spark/CODE_OF_CONDUCT.md | 17 --- bitnami/spark/CONTRIBUTING.md | 52 -------- bitnami/spark/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- .../CODE_OF_CONDUCT.md | 17 --- .../CONTRIBUTING.md | 52 -------- .../LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- .../CODE_OF_CONDUCT.md | 17 --- .../CONTRIBUTING.md | 52 -------- .../spring-cloud-dataflow-shell/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- .../spring-cloud-dataflow/CODE_OF_CONDUCT.md | 17 --- bitnami/spring-cloud-dataflow/CONTRIBUTING.md | 52 -------- bitnami/spring-cloud-dataflow/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- .../CODE_OF_CONDUCT.md | 17 --- .../CONTRIBUTING.md | 52 -------- bitnami/spring-cloud-skipper-shell/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- .../spring-cloud-skipper/CODE_OF_CONDUCT.md | 17 --- bitnami/spring-cloud-skipper/CONTRIBUTING.md | 52 -------- bitnami/spring-cloud-skipper/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../suitecrm/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/suitecrm/.github/workflows/stale.yml | 20 --- bitnami/suitecrm/CODE_OF_CONDUCT.md | 17 --- bitnami/suitecrm/CONTRIBUTING.md | 52 -------- bitnami/suitecrm/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../symfony/.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../symfony/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/symfony/.github/workflows/stale.yml | 20 --- bitnami/symfony/CODE_OF_CONDUCT.md | 17 --- bitnami/symfony/CONTRIBUTING.md | 52 -------- bitnami/symfony/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../telegraf/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/telegraf/.github/workflows/stale.yml | 20 --- bitnami/telegraf/CODE_OF_CONDUCT.md | 17 --- bitnami/telegraf/CONTRIBUTING.md | 52 -------- bitnami/telegraf/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE.md | 21 ---- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- bitnami/tensorflow-intel/CODE_OF_CONDUCT.md | 17 --- bitnami/tensorflow-intel/CONTRIBUTING.md | 52 -------- bitnami/tensorflow-intel/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- bitnami/tensorflow-resnet/CODE_OF_CONDUCT.md | 17 --- bitnami/tensorflow-resnet/CONTRIBUTING.md | 52 -------- bitnami/tensorflow-resnet/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- bitnami/tensorflow-serving/CODE_OF_CONDUCT.md | 17 --- bitnami/tensorflow-serving/CONTRIBUTING.md | 52 -------- bitnami/tensorflow-serving/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../testlink/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/testlink/.github/workflows/stale.yml | 20 --- bitnami/testlink/CODE_OF_CONDUCT.md | 17 --- bitnami/testlink/CONTRIBUTING.md | 52 -------- bitnami/testlink/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../tests/.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../tests/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/tests/.github/workflows/stale.yml | 20 --- bitnami/tests/CODE_OF_CONDUCT.md | 17 --- bitnami/tests/CONTRIBUTING.md | 52 -------- bitnami/tests/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../thanos/.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../thanos/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/thanos/.github/workflows/stale.yml | 20 --- bitnami/thanos/CODE_OF_CONDUCT.md | 17 --- bitnami/thanos/CONTRIBUTING.md | 52 -------- bitnami/thanos/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../tomcat/.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../tomcat/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/tomcat/.github/workflows/stale.yml | 20 --- bitnami/tomcat/CODE_OF_CONDUCT.md | 17 --- bitnami/tomcat/CONTRIBUTING.md | 52 -------- bitnami/tomcat/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../trivy/.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../trivy/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/trivy/.github/workflows/stale.yml | 20 --- bitnami/trivy/CODE_OF_CONDUCT.md | 17 --- bitnami/trivy/CONTRIBUTING.md | 52 -------- bitnami/trivy/LICENSE.md | 13 -- bitnami/user-broker/.github/ISSUE_TEMPLATE.md | 22 ---- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../user-broker/.github/workflows/stale.yml | 20 --- bitnami/user-broker/CODE_OF_CONDUCT.md | 17 --- bitnami/user-broker/CONTRIBUTING.md | 52 -------- bitnami/user-broker/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../wal-g/.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../wal-g/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/wal-g/.github/workflows/stale.yml | 20 --- bitnami/wal-g/CODE_OF_CONDUCT.md | 17 --- bitnami/wal-g/CONTRIBUTING.md | 52 -------- bitnami/wal-g/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- .../CODE_OF_CONDUCT.md | 17 --- .../CONTRIBUTING.md | 52 -------- .../wavefront-adapter-for-istio/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- .../wavefront-hpa-adapter/CODE_OF_CONDUCT.md | 17 --- bitnami/wavefront-hpa-adapter/CONTRIBUTING.md | 52 -------- bitnami/wavefront-hpa-adapter/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- .../CODE_OF_CONDUCT.md | 17 --- .../CONTRIBUTING.md | 52 -------- .../wavefront-kubernetes-collector/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- .../CODE_OF_CONDUCT.md | 17 --- .../CONTRIBUTING.md | 52 -------- .../LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- bitnami/wavefront-proxy/CODE_OF_CONDUCT.md | 17 --- bitnami/wavefront-proxy/CONTRIBUTING.md | 52 -------- bitnami/wavefront-proxy/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../wildfly/.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../wildfly/.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/wildfly/.github/workflows/stale.yml | 20 --- bitnami/wildfly/CODE_OF_CONDUCT.md | 17 --- bitnami/wildfly/CONTRIBUTING.md | 52 -------- bitnami/wildfly/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- bitnami/wordpress-intel/CODE_OF_CONDUCT.md | 17 --- bitnami/wordpress-intel/CONTRIBUTING.md | 52 -------- bitnami/wordpress-intel/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- .../.github/workflows/stale.yml | 20 --- bitnami/wordpress-nginx/CODE_OF_CONDUCT.md | 17 --- bitnami/wordpress-nginx/CONTRIBUTING.md | 52 -------- bitnami/wordpress-nginx/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/wordpress/.github/workflows/stale.yml | 20 --- bitnami/wordpress/CODE_OF_CONDUCT.md | 17 --- bitnami/wordpress/CONTRIBUTING.md | 52 -------- bitnami/wordpress/LICENSE.md | 13 -- .../.github/ISSUE_TEMPLATE/bug_report.yml | 41 ------ .../.github/ISSUE_TEMPLATE/config.yml | 1 - .../ISSUE_TEMPLATE/feature_request.yml | 29 ----- .../.github/PULL_REQUEST_TEMPLATE.md | 32 ----- bitnami/zookeeper/.github/workflows/stale.yml | 20 --- bitnami/zookeeper/CODE_OF_CONDUCT.md | 17 --- bitnami/zookeeper/CONTRIBUTING.md | 52 -------- bitnami/zookeeper/LICENSE.md | 13 -- scripts/fetch-commits.sh | 118 ++++++++++++++++++ scripts/sync-repos.sh | 45 +------ 1772 files changed, 141 insertions(+), 45265 deletions(-) rename {bitnami/acmesolver/.github => .github}/ISSUE_TEMPLATE/bug_report.yml (100%) rename {bitnami/acmesolver/.github => .github}/ISSUE_TEMPLATE/config.yml (100%) rename {bitnami/acmesolver/.github => .github}/ISSUE_TEMPLATE/feature_request.yml (100%) rename {bitnami/acmesolver/.github => .github}/PULL_REQUEST_TEMPLATE.md (100%) rename {bitnami/acmesolver/.github => .github}/workflows/stale.yml (100%) create mode 100644 .github/workflows/sync.yaml delete mode 100644 bitnami/acmesolver/CODE_OF_CONDUCT.md delete mode 100644 bitnami/acmesolver/CONTRIBUTING.md delete mode 100644 bitnami/acmesolver/LICENSE.md delete mode 100644 bitnami/airflow-exporter/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/airflow-exporter/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/airflow-exporter/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/airflow-exporter/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/airflow-exporter/.github/workflows/stale.yml delete mode 100644 bitnami/airflow-exporter/CODE_OF_CONDUCT.md delete mode 100644 bitnami/airflow-exporter/CONTRIBUTING.md delete mode 100644 bitnami/airflow-exporter/LICENSE.md delete mode 100644 bitnami/airflow-scheduler/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/airflow-scheduler/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/airflow-scheduler/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/airflow-scheduler/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/airflow-scheduler/.github/workflows/stale.yml delete mode 100644 bitnami/airflow-scheduler/CODE_OF_CONDUCT.md delete mode 100644 bitnami/airflow-scheduler/CONTRIBUTING.md delete mode 100644 bitnami/airflow-scheduler/LICENSE.md delete mode 100644 bitnami/airflow-worker/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/airflow-worker/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/airflow-worker/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/airflow-worker/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/airflow-worker/.github/workflows/stale.yml delete mode 100644 bitnami/airflow-worker/CODE_OF_CONDUCT.md delete mode 100644 bitnami/airflow-worker/CONTRIBUTING.md delete mode 100644 bitnami/airflow-worker/LICENSE.md delete mode 100644 bitnami/airflow/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/airflow/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/airflow/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/airflow/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/airflow/.github/workflows/stale.yml delete mode 100644 bitnami/airflow/CODE_OF_CONDUCT.md delete mode 100644 bitnami/airflow/CONTRIBUTING.md delete mode 100644 bitnami/airflow/LICENSE.md delete mode 100644 bitnami/alertmanager/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/alertmanager/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/alertmanager/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/alertmanager/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/alertmanager/.github/workflows/stale.yml delete mode 100644 bitnami/alertmanager/CODE_OF_CONDUCT.md delete mode 100644 bitnami/alertmanager/CONTRIBUTING.md delete mode 100644 bitnami/alertmanager/LICENSE.md delete mode 100644 bitnami/apache-exporter/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/apache-exporter/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/apache-exporter/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/apache-exporter/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/apache-exporter/.github/workflows/stale.yml delete mode 100644 bitnami/apache-exporter/CODE_OF_CONDUCT.md delete mode 100644 bitnami/apache-exporter/CONTRIBUTING.md delete mode 100644 bitnami/apache-exporter/LICENSE.md delete mode 100644 bitnami/apache/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/apache/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/apache/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/apache/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/apache/.github/workflows/stale.yml delete mode 100644 bitnami/apache/CODE_OF_CONDUCT.md delete mode 100644 bitnami/apache/CONTRIBUTING.md delete mode 100644 bitnami/apache/LICENSE.md delete mode 100644 bitnami/argo-cd/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/argo-cd/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/argo-cd/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/argo-cd/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/argo-cd/.github/workflows/stale.yml delete mode 100644 bitnami/argo-cd/CODE_OF_CONDUCT.md delete mode 100644 bitnami/argo-cd/CONTRIBUTING.md delete mode 100644 bitnami/argo-cd/LICENSE.md delete mode 100644 bitnami/argo-workflow-cli/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/argo-workflow-cli/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/argo-workflow-cli/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/argo-workflow-cli/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/argo-workflow-cli/.github/workflows/stale.yml delete mode 100644 bitnami/argo-workflow-cli/CODE_OF_CONDUCT.md delete mode 100644 bitnami/argo-workflow-cli/CONTRIBUTING.md delete mode 100644 bitnami/argo-workflow-cli/LICENSE.md delete mode 100644 bitnami/argo-workflow-controller/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/argo-workflow-controller/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/argo-workflow-controller/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/argo-workflow-controller/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/argo-workflow-controller/.github/workflows/stale.yml delete mode 100644 bitnami/argo-workflow-controller/CODE_OF_CONDUCT.md delete mode 100644 bitnami/argo-workflow-controller/CONTRIBUTING.md delete mode 100644 bitnami/argo-workflow-controller/LICENSE.md delete mode 100644 bitnami/argo-workflow-exec/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/argo-workflow-exec/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/argo-workflow-exec/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/argo-workflow-exec/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/argo-workflow-exec/.github/workflows/stale.yml delete mode 100644 bitnami/argo-workflow-exec/CODE_OF_CONDUCT.md delete mode 100644 bitnami/argo-workflow-exec/CONTRIBUTING.md delete mode 100644 bitnami/argo-workflow-exec/LICENSE.md delete mode 100644 bitnami/aspnet-core/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/aspnet-core/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/aspnet-core/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/aspnet-core/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/aspnet-core/.github/workflows/stale.yml delete mode 100644 bitnami/aspnet-core/CODE_OF_CONDUCT.md delete mode 100644 bitnami/aspnet-core/CONTRIBUTING.md delete mode 100644 bitnami/aspnet-core/LICENSE.md delete mode 100644 bitnami/aws-cli/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/aws-cli/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/aws-cli/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/aws-cli/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/aws-cli/.github/workflows/stale.yml delete mode 100644 bitnami/aws-cli/CODE_OF_CONDUCT.md delete mode 100644 bitnami/aws-cli/CONTRIBUTING.md delete mode 100644 bitnami/aws-cli/LICENSE.md delete mode 100644 bitnami/azure-cli/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/azure-cli/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/azure-cli/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/azure-cli/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/azure-cli/.github/workflows/stale.yml delete mode 100644 bitnami/azure-cli/CODE_OF_CONDUCT.md delete mode 100644 bitnami/azure-cli/CONTRIBUTING.md delete mode 100644 bitnami/azure-cli/LICENSE.md delete mode 100644 bitnami/bitnami-shell/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/bitnami-shell/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/bitnami-shell/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/bitnami-shell/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/bitnami-shell/.github/workflows/stale.yml delete mode 100644 bitnami/bitnami-shell/CODE_OF_CONDUCT.md delete mode 100644 bitnami/bitnami-shell/CONTRIBUTING.md delete mode 100644 bitnami/bitnami-shell/LICENSE.md delete mode 100644 bitnami/blackbox-exporter/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/blackbox-exporter/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/blackbox-exporter/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/blackbox-exporter/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/blackbox-exporter/.github/workflows/stale.yml delete mode 100644 bitnami/blackbox-exporter/CODE_OF_CONDUCT.md delete mode 100644 bitnami/blackbox-exporter/CONTRIBUTING.md delete mode 100644 bitnami/blackbox-exporter/LICENSE.md delete mode 100644 bitnami/cainjector/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/cainjector/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/cainjector/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/cainjector/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/cainjector/.github/workflows/stale.yml delete mode 100644 bitnami/cainjector/CODE_OF_CONDUCT.md delete mode 100644 bitnami/cainjector/CONTRIBUTING.md delete mode 100644 bitnami/cainjector/LICENSE.md delete mode 100644 bitnami/cassandra-exporter/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/cassandra-exporter/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/cassandra-exporter/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/cassandra-exporter/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/cassandra-exporter/.github/workflows/stale.yml delete mode 100644 bitnami/cassandra-exporter/CODE_OF_CONDUCT.md delete mode 100644 bitnami/cassandra-exporter/CONTRIBUTING.md delete mode 100644 bitnami/cassandra-exporter/LICENSE.md delete mode 100644 bitnami/cassandra/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/cassandra/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/cassandra/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/cassandra/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/cassandra/.github/workflows/stale.yml delete mode 100644 bitnami/cassandra/CODE_OF_CONDUCT.md delete mode 100644 bitnami/cassandra/CONTRIBUTING.md delete mode 100644 bitnami/cassandra/LICENSE.md delete mode 100644 bitnami/cert-manager-webhook/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/cert-manager-webhook/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/cert-manager-webhook/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/cert-manager-webhook/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/cert-manager-webhook/.github/workflows/stale.yml delete mode 100644 bitnami/cert-manager-webhook/CODE_OF_CONDUCT.md delete mode 100644 bitnami/cert-manager-webhook/CONTRIBUTING.md delete mode 100644 bitnami/cert-manager-webhook/LICENSE.md delete mode 100644 bitnami/cert-manager/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/cert-manager/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/cert-manager/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/cert-manager/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/cert-manager/.github/workflows/stale.yml delete mode 100644 bitnami/cert-manager/CODE_OF_CONDUCT.md delete mode 100644 bitnami/cert-manager/CONTRIBUTING.md delete mode 100644 bitnami/cert-manager/LICENSE.md delete mode 100644 bitnami/chartmuseum/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/chartmuseum/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/chartmuseum/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/chartmuseum/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/chartmuseum/.github/workflows/stale.yml delete mode 100644 bitnami/chartmuseum/CODE_OF_CONDUCT.md delete mode 100644 bitnami/chartmuseum/CONTRIBUTING.md delete mode 100644 bitnami/chartmuseum/LICENSE.md delete mode 100644 bitnami/cluster-autoscaler/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/cluster-autoscaler/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/cluster-autoscaler/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/cluster-autoscaler/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/cluster-autoscaler/.github/workflows/stale.yml delete mode 100644 bitnami/cluster-autoscaler/CODE_OF_CONDUCT.md delete mode 100644 bitnami/cluster-autoscaler/CONTRIBUTING.md delete mode 100644 bitnami/cluster-autoscaler/LICENSE.md delete mode 100644 bitnami/codeigniter/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/codeigniter/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/codeigniter/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/codeigniter/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/codeigniter/.github/workflows/stale.yml delete mode 100644 bitnami/codeigniter/CODE_OF_CONDUCT.md delete mode 100644 bitnami/codeigniter/CONTRIBUTING.md delete mode 100644 bitnami/codeigniter/LICENSE.md delete mode 100644 bitnami/concourse/.github/bug_report.yml delete mode 100644 bitnami/concourse/.github/config.yml delete mode 100644 bitnami/concourse/.github/feature_request.yml delete mode 100644 bitnami/concourse/CONTRIBUTING.md delete mode 100644 bitnami/concourse/LICENSE.md delete mode 100644 bitnami/configmap-reload/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/configmap-reload/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/configmap-reload/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/configmap-reload/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/configmap-reload/.github/workflows/stale.yml delete mode 100644 bitnami/configmap-reload/CODE_OF_CONDUCT.md delete mode 100644 bitnami/configmap-reload/CONTRIBUTING.md delete mode 100644 bitnami/configmap-reload/LICENSE.md delete mode 100644 bitnami/configurable-http-proxy/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/configurable-http-proxy/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/configurable-http-proxy/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/configurable-http-proxy/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/configurable-http-proxy/.github/workflows/stale.yml delete mode 100644 bitnami/configurable-http-proxy/CODE_OF_CONDUCT.md delete mode 100644 bitnami/configurable-http-proxy/CONTRIBUTING.md delete mode 100644 bitnami/configurable-http-proxy/LICENSE.md delete mode 100644 bitnami/consul-exporter/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/consul-exporter/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/consul-exporter/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/consul-exporter/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/consul-exporter/.github/workflows/stale.yml delete mode 100644 bitnami/consul-exporter/CODE_OF_CONDUCT.md delete mode 100644 bitnami/consul-exporter/CONTRIBUTING.md delete mode 100644 bitnami/consul-exporter/LICENSE.md delete mode 100644 bitnami/consul/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/consul/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/consul/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/consul/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/consul/.github/workflows/stale.yml delete mode 100644 bitnami/consul/CODE_OF_CONDUCT.md delete mode 100644 bitnami/consul/CONTRIBUTING.md delete mode 100644 bitnami/consul/LICENSE.md delete mode 100644 bitnami/contour-operator/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/contour-operator/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/contour-operator/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/contour-operator/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/contour-operator/.github/workflows/stale.yml delete mode 100644 bitnami/contour-operator/CODE_OF_CONDUCT.md delete mode 100644 bitnami/contour-operator/CONTRIBUTING.md delete mode 100644 bitnami/contour-operator/LICENSE.md delete mode 100644 bitnami/contour/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/contour/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/contour/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/contour/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/contour/.github/workflows/stale.yml delete mode 100644 bitnami/contour/CODE_OF_CONDUCT.md delete mode 100644 bitnami/contour/CONTRIBUTING.md delete mode 100644 bitnami/contour/LICENSE.md delete mode 100644 bitnami/cosign/.github/ISSUE_TEMPLATE.md delete mode 100644 bitnami/cosign/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/cosign/.github/workflows/stale.yml delete mode 100644 bitnami/cosign/CODE_OF_CONDUCT.md delete mode 100644 bitnami/cosign/CONTRIBUTING.md delete mode 100644 bitnami/cosign/LICENSE.md delete mode 100644 bitnami/couchdb/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/couchdb/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/couchdb/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/couchdb/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/couchdb/.github/workflows/stale.yml delete mode 100644 bitnami/couchdb/CODE_OF_CONDUCT.md delete mode 100644 bitnami/couchdb/CONTRIBUTING.md delete mode 100644 bitnami/couchdb/LICENSE.md delete mode 100644 bitnami/dataplatform-emitter/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/dataplatform-emitter/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/dataplatform-emitter/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/dataplatform-emitter/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/dataplatform-emitter/.github/workflows/stale.yml delete mode 100644 bitnami/dataplatform-emitter/CODE_OF_CONDUCT.md delete mode 100644 bitnami/dataplatform-emitter/CONTRIBUTING.md delete mode 100644 bitnami/dataplatform-emitter/LICENSE.md delete mode 100644 bitnami/dataplatform-exporter/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/dataplatform-exporter/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/dataplatform-exporter/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/dataplatform-exporter/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/dataplatform-exporter/.github/workflows/stale.yml delete mode 100644 bitnami/dataplatform-exporter/CODE_OF_CONDUCT.md delete mode 100644 bitnami/dataplatform-exporter/CONTRIBUTING.md delete mode 100644 bitnami/dataplatform-exporter/LICENSE.md delete mode 100644 bitnami/dex/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/dex/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/dex/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/dex/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/dex/.github/workflows/stale.yml delete mode 100644 bitnami/dex/CODE_OF_CONDUCT.md delete mode 100644 bitnami/dex/CONTRIBUTING.md delete mode 100644 bitnami/dex/LICENSE.md delete mode 100644 bitnami/discourse/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/discourse/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/discourse/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/discourse/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/discourse/.github/workflows/stale.yml delete mode 100644 bitnami/discourse/CODE_OF_CONDUCT.md delete mode 100644 bitnami/discourse/CONTRIBUTING.md delete mode 100644 bitnami/discourse/LICENSE.md delete mode 100644 bitnami/dokuwiki/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/dokuwiki/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/dokuwiki/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/dokuwiki/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/dokuwiki/.github/workflows/stale.yml delete mode 100644 bitnami/dokuwiki/CODE_OF_CONDUCT.md delete mode 100644 bitnami/dokuwiki/CONTRIBUTING.md delete mode 100644 bitnami/dokuwiki/LICENSE.md delete mode 100644 bitnami/dotnet-sdk/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/dotnet-sdk/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/dotnet-sdk/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/dotnet-sdk/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/dotnet-sdk/.github/workflows/stale.yml delete mode 100644 bitnami/dotnet-sdk/CODE_OF_CONDUCT.md delete mode 100644 bitnami/dotnet-sdk/CONTRIBUTING.md delete mode 100644 bitnami/dotnet-sdk/LICENSE.md delete mode 100644 bitnami/dotnet/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/dotnet/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/dotnet/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/dotnet/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/dotnet/.github/workflows/stale.yml delete mode 100644 bitnami/dotnet/CODE_OF_CONDUCT.md delete mode 100644 bitnami/dotnet/CONTRIBUTING.md delete mode 100644 bitnami/dotnet/LICENSE.md delete mode 100644 bitnami/dreamfactory/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/dreamfactory/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/dreamfactory/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/dreamfactory/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/dreamfactory/.github/workflows/stale.yml delete mode 100644 bitnami/dreamfactory/CODE_OF_CONDUCT.md delete mode 100644 bitnami/dreamfactory/CONTRIBUTING.md delete mode 100644 bitnami/dreamfactory/LICENSE.md delete mode 100644 bitnami/drupal-nginx/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/drupal-nginx/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/drupal-nginx/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/drupal-nginx/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/drupal-nginx/.github/workflows/stale.yml delete mode 100644 bitnami/drupal-nginx/CODE_OF_CONDUCT.md delete mode 100644 bitnami/drupal-nginx/CONTRIBUTING.md delete mode 100644 bitnami/drupal-nginx/LICENSE.md delete mode 100644 bitnami/drupal/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/drupal/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/drupal/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/drupal/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/drupal/.github/workflows/stale.yml delete mode 100644 bitnami/drupal/CODE_OF_CONDUCT.md delete mode 100644 bitnami/drupal/CONTRIBUTING.md delete mode 100644 bitnami/drupal/LICENSE.md delete mode 100644 bitnami/ejbca/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/ejbca/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/ejbca/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/ejbca/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/ejbca/.github/workflows/stale.yml delete mode 100644 bitnami/ejbca/CODE_OF_CONDUCT.md delete mode 100644 bitnami/ejbca/CONTRIBUTING.md delete mode 100644 bitnami/ejbca/LICENSE.md delete mode 100644 bitnami/elasticsearch-curator/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/elasticsearch-curator/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/elasticsearch-curator/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/elasticsearch-curator/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/elasticsearch-curator/.github/workflows/stale.yml delete mode 100644 bitnami/elasticsearch-curator/CODE_OF_CONDUCT.md delete mode 100644 bitnami/elasticsearch-curator/CONTRIBUTING.md delete mode 100644 bitnami/elasticsearch-curator/LICENSE.md delete mode 100644 bitnami/elasticsearch-exporter/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/elasticsearch-exporter/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/elasticsearch-exporter/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/elasticsearch-exporter/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/elasticsearch-exporter/.github/workflows/stale.yml delete mode 100644 bitnami/elasticsearch-exporter/CODE_OF_CONDUCT.md delete mode 100644 bitnami/elasticsearch-exporter/CONTRIBUTING.md delete mode 100644 bitnami/elasticsearch-exporter/LICENSE.md delete mode 100644 bitnami/elasticsearch/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/elasticsearch/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/elasticsearch/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/elasticsearch/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/elasticsearch/.github/workflows/stale.yml delete mode 100644 bitnami/elasticsearch/CODE_OF_CONDUCT.md delete mode 100644 bitnami/elasticsearch/CONTRIBUTING.md delete mode 100644 bitnami/elasticsearch/LICENSE.md delete mode 100644 bitnami/envoy/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/envoy/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/envoy/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/envoy/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/envoy/.github/workflows/stale.yml delete mode 100644 bitnami/envoy/CODE_OF_CONDUCT.md delete mode 100644 bitnami/envoy/CONTRIBUTING.md delete mode 100644 bitnami/envoy/LICENSE.md delete mode 100644 bitnami/etcd/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/etcd/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/etcd/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/etcd/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/etcd/.github/workflows/stale.yml delete mode 100644 bitnami/etcd/CODE_OF_CONDUCT.md delete mode 100644 bitnami/etcd/CONTRIBUTING.md delete mode 100644 bitnami/etcd/LICENSE.md delete mode 100644 bitnami/express/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/express/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/express/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/express/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/express/.github/workflows/stale.yml delete mode 100644 bitnami/express/CODE_OF_CONDUCT.md delete mode 100644 bitnami/express/CONTRIBUTING.md delete mode 100644 bitnami/express/LICENSE.md delete mode 100644 bitnami/external-dns/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/external-dns/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/external-dns/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/external-dns/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/external-dns/.github/workflows/stale.yml delete mode 100644 bitnami/external-dns/CODE_OF_CONDUCT.md delete mode 100644 bitnami/external-dns/CONTRIBUTING.md delete mode 100644 bitnami/external-dns/LICENSE.md delete mode 100644 bitnami/fluent-bit/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/fluent-bit/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/fluent-bit/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/fluent-bit/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/fluent-bit/.github/workflows/stale.yml delete mode 100644 bitnami/fluent-bit/CODE_OF_CONDUCT.md delete mode 100644 bitnami/fluent-bit/CONTRIBUTING.md delete mode 100644 bitnami/fluent-bit/LICENSE.md delete mode 100644 bitnami/fluentd-exporter/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/fluentd-exporter/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/fluentd-exporter/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/fluentd-exporter/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/fluentd-exporter/.github/workflows/stale.yml delete mode 100644 bitnami/fluentd-exporter/CODE_OF_CONDUCT.md delete mode 100644 bitnami/fluentd-exporter/CONTRIBUTING.md delete mode 100644 bitnami/fluentd-exporter/LICENSE.md delete mode 100644 bitnami/fluentd/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/fluentd/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/fluentd/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/fluentd/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/fluentd/.github/workflows/stale.yml delete mode 100644 bitnami/fluentd/CODE_OF_CONDUCT.md delete mode 100644 bitnami/fluentd/CONTRIBUTING.md delete mode 100644 bitnami/fluentd/LICENSE.md delete mode 100644 bitnami/geode/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/geode/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/geode/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/geode/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/geode/.github/stale.yml delete mode 100644 bitnami/geode/.github/workflows/stale.yml delete mode 100644 bitnami/geode/CODE_OF_CONDUCT.md delete mode 100644 bitnami/geode/CONTRIBUTING.md delete mode 100644 bitnami/geode/LICENSE.md delete mode 100644 bitnami/ghost/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/ghost/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/ghost/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/ghost/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/ghost/.github/workflows/stale.yml delete mode 100644 bitnami/ghost/CODE_OF_CONDUCT.md delete mode 100644 bitnami/ghost/CONTRIBUTING.md delete mode 100644 bitnami/ghost/LICENSE.md delete mode 100644 bitnami/git/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/git/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/git/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/git/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/git/.github/workflows/stale.yml delete mode 100644 bitnami/git/CODE_OF_CONDUCT.md delete mode 100644 bitnami/git/CONTRIBUTING.md delete mode 100644 bitnami/git/LICENSE.md delete mode 100644 bitnami/gitlab-runner-helper/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/gitlab-runner-helper/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/gitlab-runner-helper/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/gitlab-runner-helper/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/gitlab-runner-helper/.github/workflows/stale.yml delete mode 100644 bitnami/gitlab-runner-helper/CODE_OF_CONDUCT.md delete mode 100644 bitnami/gitlab-runner-helper/CONTRIBUTING.md delete mode 100644 bitnami/gitlab-runner-helper/LICENSE.md delete mode 100644 bitnami/gitlab-runner/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/gitlab-runner/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/gitlab-runner/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/gitlab-runner/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/gitlab-runner/.github/workflows/stale.yml delete mode 100644 bitnami/gitlab-runner/CODE_OF_CONDUCT.md delete mode 100644 bitnami/gitlab-runner/CONTRIBUTING.md delete mode 100644 bitnami/gitlab-runner/LICENSE.md delete mode 100644 bitnami/golang/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/golang/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/golang/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/golang/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/golang/.github/workflows/stale.yml delete mode 100644 bitnami/golang/CODE_OF_CONDUCT.md delete mode 100644 bitnami/golang/CONTRIBUTING.md delete mode 100644 bitnami/golang/LICENSE.md delete mode 100644 bitnami/google-cloud-sdk/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/google-cloud-sdk/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/google-cloud-sdk/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/google-cloud-sdk/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/google-cloud-sdk/.github/workflows/stale.yml delete mode 100644 bitnami/google-cloud-sdk/CODE_OF_CONDUCT.md delete mode 100644 bitnami/google-cloud-sdk/CONTRIBUTING.md delete mode 100644 bitnami/google-cloud-sdk/LICENSE.md delete mode 100644 bitnami/gradle/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/gradle/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/gradle/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/gradle/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/gradle/.github/workflows/stale.yml delete mode 100644 bitnami/gradle/CODE_OF_CONDUCT.md delete mode 100644 bitnami/gradle/CONTRIBUTING.md delete mode 100644 bitnami/gradle/LICENSE.md delete mode 100644 bitnami/grafana-image-renderer/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/grafana-image-renderer/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/grafana-image-renderer/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/grafana-image-renderer/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/grafana-image-renderer/.github/workflows/stale.yml delete mode 100644 bitnami/grafana-image-renderer/CODE_OF_CONDUCT.md delete mode 100644 bitnami/grafana-image-renderer/CONTRIBUTING.md delete mode 100644 bitnami/grafana-image-renderer/LICENSE.md delete mode 100644 bitnami/grafana-operator/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/grafana-operator/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/grafana-operator/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/grafana-operator/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/grafana-operator/.github/workflows/stale.yml delete mode 100644 bitnami/grafana-operator/CODE_OF_CONDUCT.md delete mode 100644 bitnami/grafana-operator/CONTRIBUTING.md delete mode 100644 bitnami/grafana-operator/LICENSE.md delete mode 100644 bitnami/grafana-tempo-query/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/grafana-tempo-query/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/grafana-tempo-query/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/grafana-tempo-query/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/grafana-tempo-query/.github/workflows/stale.yml delete mode 100644 bitnami/grafana-tempo-query/CODE_OF_CONDUCT.md delete mode 100644 bitnami/grafana-tempo-query/CONTRIBUTING.md delete mode 100644 bitnami/grafana-tempo-query/LICENSE.md delete mode 100644 bitnami/grafana-tempo-vulture/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/grafana-tempo-vulture/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/grafana-tempo-vulture/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/grafana-tempo-vulture/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/grafana-tempo-vulture/.github/workflows/stale.yml delete mode 100644 bitnami/grafana-tempo-vulture/CODE_OF_CONDUCT.md delete mode 100644 bitnami/grafana-tempo-vulture/CONTRIBUTING.md delete mode 100644 bitnami/grafana-tempo-vulture/LICENSE.md delete mode 100644 bitnami/grafana-tempo/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/grafana-tempo/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/grafana-tempo/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/grafana-tempo/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/grafana-tempo/.github/workflows/stale.yml delete mode 100644 bitnami/grafana-tempo/CODE_OF_CONDUCT.md delete mode 100644 bitnami/grafana-tempo/CONTRIBUTING.md delete mode 100644 bitnami/grafana-tempo/LICENSE.md delete mode 100644 bitnami/grafana/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/grafana/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/grafana/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/grafana/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/grafana/.github/workflows/stale.yml delete mode 100644 bitnami/grafana/CODE_OF_CONDUCT.md delete mode 100644 bitnami/grafana/CONTRIBUTING.md delete mode 100644 bitnami/grafana/LICENSE.md delete mode 100644 bitnami/haproxy/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/haproxy/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/haproxy/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/haproxy/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/haproxy/.github/workflows/stale.yml delete mode 100644 bitnami/haproxy/CODE_OF_CONDUCT.md delete mode 100644 bitnami/haproxy/CONTRIBUTING.md delete mode 100644 bitnami/haproxy/LICENSE.md delete mode 100644 bitnami/harbor-adapter-clair/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/harbor-adapter-clair/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/harbor-adapter-clair/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/harbor-adapter-clair/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/harbor-adapter-clair/.github/workflows/stale.yml delete mode 100644 bitnami/harbor-adapter-clair/CODE_OF_CONDUCT.md delete mode 100644 bitnami/harbor-adapter-clair/CONTRIBUTING.md delete mode 100644 bitnami/harbor-adapter-clair/LICENSE.md delete mode 100644 bitnami/harbor-adapter-trivy/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/harbor-adapter-trivy/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/harbor-adapter-trivy/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/harbor-adapter-trivy/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/harbor-adapter-trivy/.github/workflows/stale.yml delete mode 100644 bitnami/harbor-adapter-trivy/CODE_OF_CONDUCT.md delete mode 100644 bitnami/harbor-adapter-trivy/CONTRIBUTING.md delete mode 100644 bitnami/harbor-adapter-trivy/LICENSE.md delete mode 100644 bitnami/harbor-clair/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/harbor-clair/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/harbor-clair/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/harbor-clair/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/harbor-clair/.github/workflows/stale.yml delete mode 100644 bitnami/harbor-clair/CODE_OF_CONDUCT.md delete mode 100644 bitnami/harbor-clair/CONTRIBUTING.md delete mode 100644 bitnami/harbor-clair/LICENSE.md delete mode 100644 bitnami/harbor-core/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/harbor-core/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/harbor-core/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/harbor-core/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/harbor-core/.github/workflows/stale.yml delete mode 100644 bitnami/harbor-core/CODE_OF_CONDUCT.md delete mode 100644 bitnami/harbor-core/CONTRIBUTING.md delete mode 100644 bitnami/harbor-core/LICENSE.md delete mode 100644 bitnami/harbor-exporter/.github/ISSUE_TEMPLATE.md delete mode 100644 bitnami/harbor-exporter/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/harbor-exporter/.github/workflows/stale.yml delete mode 100644 bitnami/harbor-exporter/CODE_OF_CONDUCT.md delete mode 100644 bitnami/harbor-exporter/CONTRIBUTING.md delete mode 100644 bitnami/harbor-exporter/LICENSE.md delete mode 100644 bitnami/harbor-jobservice/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/harbor-jobservice/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/harbor-jobservice/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/harbor-jobservice/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/harbor-jobservice/.github/workflows/stale.yml delete mode 100644 bitnami/harbor-jobservice/CODE_OF_CONDUCT.md delete mode 100644 bitnami/harbor-jobservice/CONTRIBUTING.md delete mode 100644 bitnami/harbor-jobservice/LICENSE.md delete mode 100644 bitnami/harbor-notary-server/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/harbor-notary-server/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/harbor-notary-server/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/harbor-notary-server/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/harbor-notary-server/.github/workflows/stale.yml delete mode 100644 bitnami/harbor-notary-server/CODE_OF_CONDUCT.md delete mode 100644 bitnami/harbor-notary-server/CONTRIBUTING.md delete mode 100644 bitnami/harbor-notary-server/LICENSE.md delete mode 100644 bitnami/harbor-notary-signer/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/harbor-notary-signer/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/harbor-notary-signer/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/harbor-notary-signer/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/harbor-notary-signer/.github/workflows/stale.yml delete mode 100644 bitnami/harbor-notary-signer/CODE_OF_CONDUCT.md delete mode 100644 bitnami/harbor-notary-signer/CONTRIBUTING.md delete mode 100644 bitnami/harbor-notary-signer/LICENSE.md delete mode 100644 bitnami/harbor-portal/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/harbor-portal/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/harbor-portal/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/harbor-portal/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/harbor-portal/.github/workflows/stale.yml delete mode 100644 bitnami/harbor-portal/CODE_OF_CONDUCT.md delete mode 100644 bitnami/harbor-portal/CONTRIBUTING.md delete mode 100644 bitnami/harbor-portal/LICENSE.md delete mode 100644 bitnami/harbor-registry/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/harbor-registry/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/harbor-registry/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/harbor-registry/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/harbor-registry/.github/workflows/stale.yml delete mode 100644 bitnami/harbor-registry/CODE_OF_CONDUCT.md delete mode 100644 bitnami/harbor-registry/CONTRIBUTING.md delete mode 100644 bitnami/harbor-registry/LICENSE.md delete mode 100644 bitnami/harbor-registryctl/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/harbor-registryctl/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/harbor-registryctl/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/harbor-registryctl/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/harbor-registryctl/.github/workflows/stale.yml delete mode 100644 bitnami/harbor-registryctl/CODE_OF_CONDUCT.md delete mode 100644 bitnami/harbor-registryctl/CONTRIBUTING.md delete mode 100644 bitnami/harbor-registryctl/LICENSE.md delete mode 100644 bitnami/influxdb-relay/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/influxdb-relay/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/influxdb-relay/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/influxdb-relay/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/influxdb-relay/.github/workflows/stale.yml delete mode 100644 bitnami/influxdb-relay/CODE_OF_CONDUCT.md delete mode 100644 bitnami/influxdb-relay/CONTRIBUTING.md delete mode 100644 bitnami/influxdb-relay/LICENSE.md delete mode 100644 bitnami/influxdb/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/influxdb/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/influxdb/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/influxdb/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/influxdb/.github/workflows/stale.yml delete mode 100644 bitnami/influxdb/CODE_OF_CONDUCT.md delete mode 100644 bitnami/influxdb/CONTRIBUTING.md delete mode 100644 bitnami/influxdb/LICENSE.md delete mode 100644 bitnami/jasperreports/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/jasperreports/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/jasperreports/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/jasperreports/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/jasperreports/.github/workflows/stale.yml delete mode 100644 bitnami/jasperreports/CODE_OF_CONDUCT.md delete mode 100644 bitnami/jasperreports/CONTRIBUTING.md delete mode 100644 bitnami/jasperreports/LICENSE.md delete mode 100644 bitnami/java/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/java/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/java/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/java/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/java/.github/workflows/stale.yml delete mode 100644 bitnami/java/CODE_OF_CONDUCT.md delete mode 100644 bitnami/java/CONTRIBUTING.md delete mode 100644 bitnami/java/LICENSE.md delete mode 100644 bitnami/jenkins-exporter/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/jenkins-exporter/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/jenkins-exporter/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/jenkins-exporter/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/jenkins-exporter/.github/workflows/stale.yml delete mode 100644 bitnami/jenkins-exporter/CODE_OF_CONDUCT.md delete mode 100644 bitnami/jenkins-exporter/CONTRIBUTING.md delete mode 100644 bitnami/jenkins-exporter/LICENSE.md delete mode 100644 bitnami/jenkins/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/jenkins/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/jenkins/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/jenkins/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/jenkins/.github/workflows/stale.yml delete mode 100644 bitnami/jenkins/CODE_OF_CONDUCT.md delete mode 100644 bitnami/jenkins/CONTRIBUTING.md delete mode 100644 bitnami/jenkins/LICENSE.md delete mode 100644 bitnami/jmx-exporter/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/jmx-exporter/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/jmx-exporter/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/jmx-exporter/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/jmx-exporter/.github/workflows/stale.yml delete mode 100644 bitnami/jmx-exporter/CODE_OF_CONDUCT.md delete mode 100644 bitnami/jmx-exporter/CONTRIBUTING.md delete mode 100644 bitnami/jmx-exporter/LICENSE.md delete mode 100644 bitnami/joomla/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/joomla/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/joomla/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/joomla/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/joomla/.github/workflows/stale.yml delete mode 100644 bitnami/joomla/CODE_OF_CONDUCT.md delete mode 100644 bitnami/joomla/CONTRIBUTING.md delete mode 100644 bitnami/joomla/LICENSE.md delete mode 100644 bitnami/jruby/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/jruby/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/jruby/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/jruby/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/jruby/.github/workflows/stale.yml delete mode 100644 bitnami/jruby/CODE_OF_CONDUCT.md delete mode 100644 bitnami/jruby/CONTRIBUTING.md delete mode 100644 bitnami/jruby/LICENSE.md delete mode 100644 bitnami/jsonnet/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/jsonnet/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/jsonnet/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/jsonnet/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/jsonnet/.github/workflows/stale.yml delete mode 100644 bitnami/jsonnet/CODE_OF_CONDUCT.md delete mode 100644 bitnami/jsonnet/CONTRIBUTING.md delete mode 100644 bitnami/jsonnet/LICENSE.md delete mode 100644 bitnami/jupyter-base-notebook/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/jupyter-base-notebook/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/jupyter-base-notebook/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/jupyter-base-notebook/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/jupyter-base-notebook/.github/workflows/stale.yml delete mode 100644 bitnami/jupyter-base-notebook/CODE_OF_CONDUCT.md delete mode 100644 bitnami/jupyter-base-notebook/CONTRIBUTING.md delete mode 100644 bitnami/jupyter-base-notebook/LICENSE.md delete mode 100644 bitnami/jupyterhub/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/jupyterhub/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/jupyterhub/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/jupyterhub/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/jupyterhub/.github/workflows/stale.yml delete mode 100644 bitnami/jupyterhub/CODE_OF_CONDUCT.md delete mode 100644 bitnami/jupyterhub/CONTRIBUTING.md delete mode 100644 bitnami/jupyterhub/LICENSE.md delete mode 100644 bitnami/kafka-exporter/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/kafka-exporter/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/kafka-exporter/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/kafka-exporter/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/kafka-exporter/.github/workflows/stale.yml delete mode 100644 bitnami/kafka-exporter/CODE_OF_CONDUCT.md delete mode 100644 bitnami/kafka-exporter/CONTRIBUTING.md delete mode 100644 bitnami/kafka-exporter/LICENSE.md delete mode 100644 bitnami/kafka/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/kafka/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/kafka/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/kafka/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/kafka/.github/workflows/stale.yml delete mode 100644 bitnami/kafka/CODE_OF_CONDUCT.md delete mode 100644 bitnami/kafka/CONTRIBUTING.md delete mode 100644 bitnami/kafka/LICENSE.md delete mode 100644 bitnami/kapacitor/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/kapacitor/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/kapacitor/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/kapacitor/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/kapacitor/.github/workflows/stale.yml delete mode 100644 bitnami/kapacitor/CODE_OF_CONDUCT.md delete mode 100644 bitnami/kapacitor/CONTRIBUTING.md delete mode 100644 bitnami/kapacitor/LICENSE.md delete mode 100644 bitnami/keycloak-config-cli/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/keycloak-config-cli/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/keycloak-config-cli/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/keycloak-config-cli/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/keycloak-config-cli/.github/workflows/stale.yml delete mode 100644 bitnami/keycloak-config-cli/CODE_OF_CONDUCT.md delete mode 100644 bitnami/keycloak-config-cli/CONTRIBUTING.md delete mode 100644 bitnami/keycloak-config-cli/LICENSE.md delete mode 100644 bitnami/keycloak-gatekeeper/.github/ISSUE_TEMPLATE.md delete mode 100644 bitnami/keycloak-gatekeeper/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/keycloak-gatekeeper/.github/workflows/stale.yml delete mode 100644 bitnami/keycloak-gatekeeper/CODE_OF_CONDUCT.md delete mode 100644 bitnami/keycloak-gatekeeper/CONTRIBUTING.md delete mode 100644 bitnami/keycloak-gatekeeper/LICENSE.md delete mode 100644 bitnami/keycloak/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/keycloak/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/keycloak/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/keycloak/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/keycloak/.github/workflows/stale.yml delete mode 100644 bitnami/keycloak/CODE_OF_CONDUCT.md delete mode 100644 bitnami/keycloak/CONTRIBUTING.md delete mode 100644 bitnami/keycloak/LICENSE.md delete mode 100644 bitnami/kiam/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/kiam/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/kiam/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/kiam/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/kiam/.github/workflows/stale.yml delete mode 100644 bitnami/kiam/CODE_OF_CONDUCT.md delete mode 100644 bitnami/kiam/CONTRIBUTING.md delete mode 100644 bitnami/kiam/LICENSE.md delete mode 100644 bitnami/kibana/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/kibana/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/kibana/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/kibana/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/kibana/.github/workflows/stale.yml delete mode 100644 bitnami/kibana/CODE_OF_CONDUCT.md delete mode 100644 bitnami/kibana/CONTRIBUTING.md delete mode 100644 bitnami/kibana/LICENSE.md delete mode 100644 bitnami/kong-ingress-controller/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/kong-ingress-controller/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/kong-ingress-controller/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/kong-ingress-controller/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/kong-ingress-controller/.github/workflows/stale.yml delete mode 100644 bitnami/kong-ingress-controller/CODE_OF_CONDUCT.md delete mode 100644 bitnami/kong-ingress-controller/CONTRIBUTING.md delete mode 100644 bitnami/kong-ingress-controller/LICENSE.md delete mode 100644 bitnami/kong/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/kong/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/kong/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/kong/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/kong/.github/workflows/stale.yml delete mode 100644 bitnami/kong/CODE_OF_CONDUCT.md delete mode 100644 bitnami/kong/CONTRIBUTING.md delete mode 100644 bitnami/kong/LICENSE.md delete mode 100644 bitnami/kube-rbac-proxy/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/kube-rbac-proxy/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/kube-rbac-proxy/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/kube-rbac-proxy/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/kube-rbac-proxy/.github/workflows/stale.yml delete mode 100644 bitnami/kube-rbac-proxy/CODE_OF_CONDUCT.md delete mode 100644 bitnami/kube-rbac-proxy/CONTRIBUTING.md delete mode 100644 bitnami/kube-rbac-proxy/LICENSE.md delete mode 100644 bitnami/kube-state-metrics/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/kube-state-metrics/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/kube-state-metrics/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/kube-state-metrics/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/kube-state-metrics/.github/workflows/stale.yml delete mode 100644 bitnami/kube-state-metrics/CODE_OF_CONDUCT.md delete mode 100644 bitnami/kube-state-metrics/CONTRIBUTING.md delete mode 100644 bitnami/kube-state-metrics/LICENSE.md delete mode 100644 bitnami/kubeapps-apis/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/kubeapps-apis/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/kubeapps-apis/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/kubeapps-apis/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/kubeapps-apis/.github/workflows/stale.yml delete mode 100644 bitnami/kubeapps-apis/CODE_OF_CONDUCT.md delete mode 100644 bitnami/kubeapps-apis/CONTRIBUTING.md delete mode 100644 bitnami/kubeapps-apis/LICENSE.md delete mode 100644 bitnami/kubeapps-apprepository-controller/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/kubeapps-apprepository-controller/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/kubeapps-apprepository-controller/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/kubeapps-apprepository-controller/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/kubeapps-apprepository-controller/.github/workflows/stale.yml delete mode 100644 bitnami/kubeapps-apprepository-controller/CODE_OF_CONDUCT.md delete mode 100644 bitnami/kubeapps-apprepository-controller/CONTRIBUTING.md delete mode 100644 bitnami/kubeapps-apprepository-controller/LICENSE.md delete mode 100644 bitnami/kubeapps-asset-syncer/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/kubeapps-asset-syncer/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/kubeapps-asset-syncer/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/kubeapps-asset-syncer/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/kubeapps-asset-syncer/.github/workflows/stale.yml delete mode 100644 bitnami/kubeapps-asset-syncer/CODE_OF_CONDUCT.md delete mode 100644 bitnami/kubeapps-asset-syncer/CONTRIBUTING.md delete mode 100644 bitnami/kubeapps-asset-syncer/LICENSE.md delete mode 100644 bitnami/kubeapps-assetsvc/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/kubeapps-assetsvc/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/kubeapps-assetsvc/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/kubeapps-assetsvc/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/kubeapps-assetsvc/.github/workflows/stale.yml delete mode 100644 bitnami/kubeapps-assetsvc/CODE_OF_CONDUCT.md delete mode 100644 bitnami/kubeapps-assetsvc/CONTRIBUTING.md delete mode 100644 bitnami/kubeapps-assetsvc/LICENSE.md delete mode 100644 bitnami/kubeapps-dashboard/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/kubeapps-dashboard/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/kubeapps-dashboard/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/kubeapps-dashboard/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/kubeapps-dashboard/.github/workflows/stale.yml delete mode 100644 bitnami/kubeapps-dashboard/CODE_OF_CONDUCT.md delete mode 100644 bitnami/kubeapps-dashboard/CONTRIBUTING.md delete mode 100644 bitnami/kubeapps-dashboard/LICENSE.md delete mode 100644 bitnami/kubeapps-kubeops/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/kubeapps-kubeops/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/kubeapps-kubeops/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/kubeapps-kubeops/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/kubeapps-kubeops/.github/workflows/stale.yml delete mode 100644 bitnami/kubeapps-kubeops/CODE_OF_CONDUCT.md delete mode 100644 bitnami/kubeapps-kubeops/CONTRIBUTING.md delete mode 100644 bitnami/kubeapps-kubeops/LICENSE.md delete mode 100644 bitnami/kubeapps-pinniped-proxy/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/kubeapps-pinniped-proxy/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/kubeapps-pinniped-proxy/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/kubeapps-pinniped-proxy/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/kubeapps-pinniped-proxy/.github/workflows/stale.yml delete mode 100644 bitnami/kubeapps-pinniped-proxy/CODE_OF_CONDUCT.md delete mode 100644 bitnami/kubeapps-pinniped-proxy/CONTRIBUTING.md delete mode 100644 bitnami/kubeapps-pinniped-proxy/LICENSE.md delete mode 100644 bitnami/kubectl/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/kubectl/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/kubectl/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/kubectl/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/kubectl/.github/workflows/stale.yml delete mode 100644 bitnami/kubectl/CODE_OF_CONDUCT.md delete mode 100644 bitnami/kubectl/CONTRIBUTING.md delete mode 100644 bitnami/kubectl/LICENSE.md delete mode 100644 bitnami/kubernetes-event-exporter/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/kubernetes-event-exporter/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/kubernetes-event-exporter/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/kubernetes-event-exporter/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/kubernetes-event-exporter/.github/workflows/stale.yml delete mode 100644 bitnami/kubernetes-event-exporter/CODE_OF_CONDUCT.md delete mode 100644 bitnami/kubernetes-event-exporter/CONTRIBUTING.md delete mode 100644 bitnami/kubernetes-event-exporter/LICENSE.md delete mode 100644 bitnami/kubewatch/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/kubewatch/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/kubewatch/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/kubewatch/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/kubewatch/.github/workflows/stale.yml delete mode 100644 bitnami/kubewatch/CODE_OF_CONDUCT.md delete mode 100644 bitnami/kubewatch/CONTRIBUTING.md delete mode 100644 bitnami/kubewatch/LICENSE.md delete mode 100644 bitnami/laravel/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/laravel/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/laravel/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/laravel/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/laravel/.github/workflows/stale.yml delete mode 100644 bitnami/laravel/CODE_OF_CONDUCT.md delete mode 100644 bitnami/laravel/CONTRIBUTING.md delete mode 100644 bitnami/laravel/LICENSE.md delete mode 100644 bitnami/logstash-exporter/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/logstash-exporter/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/logstash-exporter/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/logstash-exporter/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/logstash-exporter/.github/workflows/stale.yml delete mode 100644 bitnami/logstash-exporter/CODE_OF_CONDUCT.md delete mode 100644 bitnami/logstash-exporter/CONTRIBUTING.md delete mode 100644 bitnami/logstash-exporter/LICENSE.md delete mode 100644 bitnami/logstash/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/logstash/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/logstash/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/logstash/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/logstash/.github/workflows/stale.yml delete mode 100644 bitnami/logstash/CODE_OF_CONDUCT.md delete mode 100644 bitnami/logstash/CONTRIBUTING.md delete mode 100644 bitnami/logstash/LICENSE.md delete mode 100644 bitnami/magento/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/magento/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/magento/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/magento/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/magento/.github/workflows/stale.yml delete mode 100644 bitnami/magento/CODE_OF_CONDUCT.md delete mode 100644 bitnami/magento/CONTRIBUTING.md delete mode 100644 bitnami/magento/LICENSE.md delete mode 100644 bitnami/mariadb-galera/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/mariadb-galera/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/mariadb-galera/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/mariadb-galera/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/mariadb-galera/.github/workflows/stale.yml delete mode 100644 bitnami/mariadb-galera/CODE_OF_CONDUCT.md delete mode 100644 bitnami/mariadb-galera/CONTRIBUTING.md delete mode 100644 bitnami/mariadb-galera/LICENSE.md delete mode 100644 bitnami/mariadb/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/mariadb/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/mariadb/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/mariadb/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/mariadb/.github/workflows/stale.yml delete mode 100644 bitnami/mariadb/CODE_OF_CONDUCT.md delete mode 100644 bitnami/mariadb/CONTRIBUTING.md delete mode 100644 bitnami/mariadb/LICENSE.md delete mode 100644 bitnami/matomo/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/matomo/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/matomo/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/matomo/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/matomo/.github/workflows/stale.yml delete mode 100644 bitnami/matomo/CODE_OF_CONDUCT.md delete mode 100644 bitnami/matomo/CONTRIBUTING.md delete mode 100644 bitnami/matomo/LICENSE.md delete mode 100644 bitnami/mediawiki/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/mediawiki/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/mediawiki/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/mediawiki/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/mediawiki/.github/workflows/stale.yml delete mode 100644 bitnami/mediawiki/CODE_OF_CONDUCT.md delete mode 100644 bitnami/mediawiki/CONTRIBUTING.md delete mode 100644 bitnami/mediawiki/LICENSE.md delete mode 100644 bitnami/memcached-exporter/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/memcached-exporter/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/memcached-exporter/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/memcached-exporter/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/memcached-exporter/.github/workflows/stale.yml delete mode 100644 bitnami/memcached-exporter/CODE_OF_CONDUCT.md delete mode 100644 bitnami/memcached-exporter/CONTRIBUTING.md delete mode 100644 bitnami/memcached-exporter/LICENSE.md delete mode 100644 bitnami/memcached/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/memcached/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/memcached/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/memcached/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/memcached/.github/workflows/stale.yml delete mode 100644 bitnami/memcached/CODE_OF_CONDUCT.md delete mode 100644 bitnami/memcached/CONTRIBUTING.md delete mode 100644 bitnami/memcached/LICENSE.md delete mode 100644 bitnami/metallb-controller/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/metallb-controller/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/metallb-controller/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/metallb-controller/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/metallb-controller/.github/workflows/stale.yml delete mode 100644 bitnami/metallb-controller/CODE_OF_CONDUCT.md delete mode 100644 bitnami/metallb-controller/CONTRIBUTING.md delete mode 100644 bitnami/metallb-controller/LICENSE.md delete mode 100644 bitnami/metallb-speaker/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/metallb-speaker/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/metallb-speaker/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/metallb-speaker/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/metallb-speaker/.github/workflows/stale.yml delete mode 100644 bitnami/metallb-speaker/CODE_OF_CONDUCT.md delete mode 100644 bitnami/metallb-speaker/CONTRIBUTING.md delete mode 100644 bitnami/metallb-speaker/LICENSE.md delete mode 100644 bitnami/metrics-server/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/metrics-server/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/metrics-server/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/metrics-server/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/metrics-server/.github/workflows/stale.yml delete mode 100644 bitnami/metrics-server/CODE_OF_CONDUCT.md delete mode 100644 bitnami/metrics-server/CONTRIBUTING.md delete mode 100644 bitnami/metrics-server/LICENSE.md delete mode 100644 bitnami/minio-client/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/minio-client/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/minio-client/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/minio-client/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/minio-client/.github/workflows/stale.yml delete mode 100644 bitnami/minio-client/CODE_OF_CONDUCT.md delete mode 100644 bitnami/minio-client/CONTRIBUTING.md delete mode 100644 bitnami/minio-client/LICENSE.md delete mode 100644 bitnami/minio/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/minio/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/minio/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/minio/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/minio/.github/workflows/stale.yml delete mode 100644 bitnami/minio/CODE_OF_CONDUCT.md delete mode 100644 bitnami/minio/CONTRIBUTING.md delete mode 100644 bitnami/minio/LICENSE.md delete mode 100644 bitnami/mongodb-exporter/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/mongodb-exporter/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/mongodb-exporter/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/mongodb-exporter/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/mongodb-exporter/.github/workflows/stale.yml delete mode 100644 bitnami/mongodb-exporter/CODE_OF_CONDUCT.md delete mode 100644 bitnami/mongodb-exporter/CONTRIBUTING.md delete mode 100644 bitnami/mongodb-exporter/LICENSE.md delete mode 100644 bitnami/mongodb-sharded/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/mongodb-sharded/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/mongodb-sharded/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/mongodb-sharded/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/mongodb-sharded/.github/workflows/stale.yml delete mode 100644 bitnami/mongodb-sharded/CODE_OF_CONDUCT.md delete mode 100644 bitnami/mongodb-sharded/CONTRIBUTING.md delete mode 100644 bitnami/mongodb-sharded/LICENSE.md delete mode 100644 bitnami/mongodb/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/mongodb/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/mongodb/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/mongodb/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/mongodb/.github/workflows/stale.yml delete mode 100644 bitnami/mongodb/CODE_OF_CONDUCT.md delete mode 100644 bitnami/mongodb/CONTRIBUTING.md delete mode 100644 bitnami/mongodb/LICENSE.md delete mode 100644 bitnami/moodle/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/moodle/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/moodle/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/moodle/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/moodle/.github/workflows/stale.yml delete mode 100644 bitnami/moodle/CODE_OF_CONDUCT.md delete mode 100644 bitnami/moodle/CONTRIBUTING.md delete mode 100644 bitnami/moodle/LICENSE.md delete mode 100644 bitnami/mxnet/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/mxnet/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/mxnet/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/mxnet/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/mxnet/.github/workflows/stale.yml delete mode 100644 bitnami/mxnet/CODE_OF_CONDUCT.md delete mode 100644 bitnami/mxnet/CONTRIBUTING.md delete mode 100644 bitnami/mxnet/LICENSE.md delete mode 100644 bitnami/mysql/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/mysql/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/mysql/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/mysql/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/mysql/.github/workflows/stale.yml delete mode 100644 bitnami/mysql/CODE_OF_CONDUCT.md delete mode 100644 bitnami/mysql/CONTRIBUTING.md delete mode 100644 bitnami/mysql/LICENSE.md delete mode 100644 bitnami/mysqld-exporter/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/mysqld-exporter/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/mysqld-exporter/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/mysqld-exporter/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/mysqld-exporter/.github/workflows/stale.yml delete mode 100644 bitnami/mysqld-exporter/CODE_OF_CONDUCT.md delete mode 100644 bitnami/mysqld-exporter/CONTRIBUTING.md delete mode 100644 bitnami/mysqld-exporter/LICENSE.md delete mode 100644 bitnami/nats-exporter/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/nats-exporter/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/nats-exporter/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/nats-exporter/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/nats-exporter/.github/workflows/stale.yml delete mode 100644 bitnami/nats-exporter/CODE_OF_CONDUCT.md delete mode 100644 bitnami/nats-exporter/CONTRIBUTING.md delete mode 100644 bitnami/nats-exporter/LICENSE.md delete mode 100644 bitnami/nats/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/nats/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/nats/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/nats/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/nats/.github/workflows/stale.yml delete mode 100644 bitnami/nats/CODE_OF_CONDUCT.md delete mode 100644 bitnami/nats/CONTRIBUTING.md delete mode 100644 bitnami/nats/LICENSE.md delete mode 100644 bitnami/neo4j/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/neo4j/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/neo4j/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/neo4j/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/neo4j/.github/workflows/stale.yml delete mode 100644 bitnami/neo4j/CODE_OF_CONDUCT.md delete mode 100644 bitnami/neo4j/CONTRIBUTING.md delete mode 100644 bitnami/neo4j/LICENSE.md delete mode 100644 bitnami/nginx-exporter/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/nginx-exporter/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/nginx-exporter/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/nginx-exporter/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/nginx-exporter/.github/workflows/stale.yml delete mode 100644 bitnami/nginx-exporter/CODE_OF_CONDUCT.md delete mode 100644 bitnami/nginx-exporter/CONTRIBUTING.md delete mode 100644 bitnami/nginx-exporter/LICENSE.md delete mode 100644 bitnami/nginx-ingress-controller/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/nginx-ingress-controller/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/nginx-ingress-controller/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/nginx-ingress-controller/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/nginx-ingress-controller/.github/workflows/stale.yml delete mode 100644 bitnami/nginx-ingress-controller/CODE_OF_CONDUCT.md delete mode 100644 bitnami/nginx-ingress-controller/CONTRIBUTING.md delete mode 100644 bitnami/nginx-ingress-controller/LICENSE.md delete mode 100644 bitnami/nginx-intel/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/nginx-intel/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/nginx-intel/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/nginx-intel/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/nginx-intel/.github/workflows/stale.yml delete mode 100644 bitnami/nginx-intel/CODE_OF_CONDUCT.md delete mode 100644 bitnami/nginx-intel/CONTRIBUTING.md delete mode 100644 bitnami/nginx-intel/LICENSE.md delete mode 100644 bitnami/nginx-ldap-auth-daemon/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/nginx-ldap-auth-daemon/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/nginx-ldap-auth-daemon/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/nginx-ldap-auth-daemon/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/nginx-ldap-auth-daemon/.github/workflows/stale.yml delete mode 100644 bitnami/nginx-ldap-auth-daemon/CODE_OF_CONDUCT.md delete mode 100644 bitnami/nginx-ldap-auth-daemon/CONTRIBUTING.md delete mode 100644 bitnami/nginx-ldap-auth-daemon/LICENSE.md delete mode 100644 bitnami/nginx/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/nginx/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/nginx/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/nginx/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/nginx/.github/workflows/stale.yml delete mode 100644 bitnami/nginx/CODE_OF_CONDUCT.md delete mode 100644 bitnami/nginx/CONTRIBUTING.md delete mode 100644 bitnami/nginx/LICENSE.md delete mode 100644 bitnami/node-exporter/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/node-exporter/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/node-exporter/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/node-exporter/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/node-exporter/.github/workflows/stale.yml delete mode 100644 bitnami/node-exporter/CODE_OF_CONDUCT.md delete mode 100644 bitnami/node-exporter/CONTRIBUTING.md delete mode 100644 bitnami/node-exporter/LICENSE.md delete mode 100644 bitnami/node-snapshot/.github/ISSUE_TEMPLATE.md delete mode 100644 bitnami/node-snapshot/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/node-snapshot/.github/workflows/stale.yml delete mode 100644 bitnami/node-snapshot/CODE_OF_CONDUCT.md delete mode 100644 bitnami/node-snapshot/CONTRIBUTING.md delete mode 100644 bitnami/node-snapshot/LICENSE.md delete mode 100644 bitnami/node/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/node/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/node/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/node/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/node/.github/workflows/stale.yml delete mode 100644 bitnami/node/CODE_OF_CONDUCT.md delete mode 100644 bitnami/node/CONTRIBUTING.md delete mode 100644 bitnami/node/LICENSE.md delete mode 100644 bitnami/oauth2-proxy/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/oauth2-proxy/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/oauth2-proxy/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/oauth2-proxy/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/oauth2-proxy/.github/workflows/stale.yml delete mode 100644 bitnami/oauth2-proxy/CODE_OF_CONDUCT.md delete mode 100644 bitnami/oauth2-proxy/CONTRIBUTING.md delete mode 100644 bitnami/oauth2-proxy/LICENSE.md delete mode 100644 bitnami/odoo/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/odoo/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/odoo/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/odoo/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/odoo/.github/workflows/stale.yml delete mode 100644 bitnami/odoo/CODE_OF_CONDUCT.md delete mode 100644 bitnami/odoo/CONTRIBUTING.md delete mode 100644 bitnami/odoo/LICENSE.md delete mode 100644 bitnami/open-service-broker-azure/.github/ISSUE_TEMPLATE.md delete mode 100644 bitnami/open-service-broker-azure/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/open-service-broker-azure/.github/workflows/stale.yml delete mode 100644 bitnami/open-service-broker-azure/CODE_OF_CONDUCT.md delete mode 100644 bitnami/open-service-broker-azure/CONTRIBUTING.md delete mode 100644 bitnami/open-service-broker-azure/LICENSE.md delete mode 100644 bitnami/opencart/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/opencart/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/opencart/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/opencart/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/opencart/.github/workflows/stale.yml delete mode 100644 bitnami/opencart/CODE_OF_CONDUCT.md delete mode 100644 bitnami/opencart/CONTRIBUTING.md delete mode 100644 bitnami/opencart/LICENSE.md delete mode 100644 bitnami/openldap/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/openldap/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/openldap/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/openldap/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/openldap/.github/workflows/stale.yml delete mode 100644 bitnami/openldap/CODE_OF_CONDUCT.md delete mode 100644 bitnami/openldap/CONTRIBUTING.md delete mode 100644 bitnami/openldap/LICENSE.md delete mode 100644 bitnami/openresty/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/openresty/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/openresty/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/openresty/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/openresty/.github/workflows/stale.yml delete mode 100644 bitnami/openresty/CODE_OF_CONDUCT.md delete mode 100644 bitnami/openresty/CONTRIBUTING.md delete mode 100644 bitnami/openresty/LICENSE.md delete mode 100644 bitnami/orangehrm/.github/ISSUE_TEMPLATE.md delete mode 100644 bitnami/orangehrm/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/orangehrm/.github/workflows/stale.yml delete mode 100644 bitnami/orangehrm/CODE_OF_CONDUCT.md delete mode 100644 bitnami/orangehrm/CONTRIBUTING.md delete mode 100644 bitnami/orangehrm/LICENSE.md delete mode 100644 bitnami/oras/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/oras/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/oras/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/oras/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/oras/.github/workflows/stale.yml delete mode 100644 bitnami/oras/CODE_OF_CONDUCT.md delete mode 100644 bitnami/oras/CONTRIBUTING.md delete mode 100644 bitnami/oras/LICENSE.md delete mode 100644 bitnami/osclass/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/osclass/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/osclass/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/osclass/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/osclass/.github/workflows/stale.yml delete mode 100644 bitnami/osclass/CODE_OF_CONDUCT.md delete mode 100644 bitnami/osclass/CONTRIBUTING.md delete mode 100644 bitnami/osclass/LICENSE.md delete mode 100644 bitnami/owncloud/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/owncloud/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/owncloud/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/owncloud/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/owncloud/.github/workflows/stale.yml delete mode 100644 bitnami/owncloud/CODE_OF_CONDUCT.md delete mode 100644 bitnami/owncloud/CONTRIBUTING.md delete mode 100644 bitnami/owncloud/LICENSE.md delete mode 100644 bitnami/parse-dashboard/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/parse-dashboard/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/parse-dashboard/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/parse-dashboard/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/parse-dashboard/.github/workflows/stale.yml delete mode 100644 bitnami/parse-dashboard/CODE_OF_CONDUCT.md delete mode 100644 bitnami/parse-dashboard/CONTRIBUTING.md delete mode 100644 bitnami/parse-dashboard/LICENSE.md delete mode 100644 bitnami/parse/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/parse/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/parse/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/parse/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/parse/.github/workflows/stale.yml delete mode 100644 bitnami/parse/CODE_OF_CONDUCT.md delete mode 100644 bitnami/parse/CONTRIBUTING.md delete mode 100644 bitnami/parse/LICENSE.md delete mode 100644 bitnami/percona-xtrabackup/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/percona-xtrabackup/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/percona-xtrabackup/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/percona-xtrabackup/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/percona-xtrabackup/.github/workflows/stale.yml delete mode 100644 bitnami/percona-xtrabackup/CODE_OF_CONDUCT.md delete mode 100644 bitnami/percona-xtrabackup/CONTRIBUTING.md delete mode 100644 bitnami/percona-xtrabackup/LICENSE.md delete mode 100644 bitnami/pgbouncer/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/pgbouncer/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/pgbouncer/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/pgbouncer/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/pgbouncer/.github/workflows/stale.yml delete mode 100644 bitnami/pgbouncer/CODE_OF_CONDUCT.md delete mode 100644 bitnami/pgbouncer/CONTRIBUTING.md delete mode 100644 bitnami/pgbouncer/LICENSE.md delete mode 100644 bitnami/pgpool/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/pgpool/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/pgpool/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/pgpool/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/pgpool/.github/workflows/stale.yml delete mode 100644 bitnami/pgpool/CODE_OF_CONDUCT.md delete mode 100644 bitnami/pgpool/CONTRIBUTING.md delete mode 100644 bitnami/pgpool/LICENSE.md delete mode 100644 bitnami/php-fpm/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/php-fpm/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/php-fpm/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/php-fpm/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/php-fpm/.github/workflows/stale.yml delete mode 100644 bitnami/php-fpm/CODE_OF_CONDUCT.md delete mode 100644 bitnami/php-fpm/CONTRIBUTING.md delete mode 100644 bitnami/php-fpm/LICENSE.md delete mode 100644 bitnami/phpbb/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/phpbb/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/phpbb/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/phpbb/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/phpbb/.github/workflows/stale.yml delete mode 100644 bitnami/phpbb/CODE_OF_CONDUCT.md delete mode 100644 bitnami/phpbb/CONTRIBUTING.md delete mode 100644 bitnami/phpbb/LICENSE.md delete mode 100644 bitnami/phpmyadmin/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/phpmyadmin/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/phpmyadmin/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/phpmyadmin/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/phpmyadmin/.github/workflows/stale.yml delete mode 100644 bitnami/phpmyadmin/CODE_OF_CONDUCT.md delete mode 100644 bitnami/phpmyadmin/CONTRIBUTING.md delete mode 100644 bitnami/phpmyadmin/LICENSE.md delete mode 100644 bitnami/phppgadmin/.github/ISSUE_TEMPLATE.md delete mode 100644 bitnami/phppgadmin/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/phppgadmin/.github/workflows/stale.yml delete mode 100644 bitnami/phppgadmin/CODE_OF_CONDUCT.md delete mode 100644 bitnami/phppgadmin/CONTRIBUTING.md delete mode 100644 bitnami/phppgadmin/LICENSE.md delete mode 100644 bitnami/postgres-exporter/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/postgres-exporter/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/postgres-exporter/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/postgres-exporter/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/postgres-exporter/.github/workflows/stale.yml delete mode 100644 bitnami/postgres-exporter/CODE_OF_CONDUCT.md delete mode 100644 bitnami/postgres-exporter/CONTRIBUTING.md delete mode 100644 bitnami/postgres-exporter/LICENSE.md delete mode 100644 bitnami/postgresql-repmgr/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/postgresql-repmgr/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/postgresql-repmgr/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/postgresql-repmgr/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/postgresql-repmgr/.github/workflows/stale.yml delete mode 100644 bitnami/postgresql-repmgr/CODE_OF_CONDUCT.md delete mode 100644 bitnami/postgresql-repmgr/CONTRIBUTING.md delete mode 100644 bitnami/postgresql-repmgr/LICENSE.md delete mode 100644 bitnami/postgresql/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/postgresql/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/postgresql/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/postgresql/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/postgresql/.github/workflows/stale.yml delete mode 100644 bitnami/postgresql/CODE_OF_CONDUCT.md delete mode 100644 bitnami/postgresql/CONTRIBUTING.md delete mode 100644 bitnami/postgresql/LICENSE.md delete mode 100644 bitnami/prestashop/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/prestashop/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/prestashop/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/prestashop/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/prestashop/.github/workflows/stale.yml delete mode 100644 bitnami/prestashop/CODE_OF_CONDUCT.md delete mode 100644 bitnami/prestashop/CONTRIBUTING.md delete mode 100644 bitnami/prestashop/LICENSE.md delete mode 100644 bitnami/prometheus-operator/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/prometheus-operator/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/prometheus-operator/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/prometheus-operator/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/prometheus-operator/.github/workflows/stale.yml delete mode 100644 bitnami/prometheus-operator/CODE_OF_CONDUCT.md delete mode 100644 bitnami/prometheus-operator/CONTRIBUTING.md delete mode 100644 bitnami/prometheus-operator/LICENSE.md delete mode 100644 bitnami/prometheus-rsocket-proxy/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/prometheus-rsocket-proxy/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/prometheus-rsocket-proxy/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/prometheus-rsocket-proxy/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/prometheus-rsocket-proxy/.github/workflows/stale.yml delete mode 100644 bitnami/prometheus-rsocket-proxy/CODE_OF_CONDUCT.md delete mode 100644 bitnami/prometheus-rsocket-proxy/CONTRIBUTING.md delete mode 100644 bitnami/prometheus-rsocket-proxy/LICENSE.md delete mode 100644 bitnami/prometheus/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/prometheus/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/prometheus/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/prometheus/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/prometheus/.github/workflows/stale.yml delete mode 100644 bitnami/prometheus/CODE_OF_CONDUCT.md delete mode 100644 bitnami/prometheus/CONTRIBUTING.md delete mode 100644 bitnami/prometheus/LICENSE.md delete mode 100644 bitnami/pushgateway/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/pushgateway/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/pushgateway/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/pushgateway/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/pushgateway/.github/workflows/stale.yml delete mode 100644 bitnami/pushgateway/CODE_OF_CONDUCT.md delete mode 100644 bitnami/pushgateway/CONTRIBUTING.md delete mode 100644 bitnami/pushgateway/LICENSE.md delete mode 100644 bitnami/python-snapshot/.github/ISSUE_TEMPLATE.md delete mode 100644 bitnami/python-snapshot/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/python-snapshot/.github/workflows/stale.yml delete mode 100644 bitnami/python-snapshot/CODE_OF_CONDUCT.md delete mode 100644 bitnami/python-snapshot/CONTRIBUTING.md delete mode 100644 bitnami/python-snapshot/LICENSE.md delete mode 100644 bitnami/python/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/python/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/python/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/python/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/python/.github/workflows/stale.yml delete mode 100644 bitnami/python/CODE_OF_CONDUCT.md delete mode 100644 bitnami/python/CONTRIBUTING.md delete mode 100644 bitnami/python/LICENSE.md delete mode 100644 bitnami/pytorch/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/pytorch/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/pytorch/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/pytorch/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/pytorch/.github/workflows/stale.yml delete mode 100644 bitnami/pytorch/CODE_OF_CONDUCT.md delete mode 100644 bitnami/pytorch/CONTRIBUTING.md delete mode 100644 bitnami/pytorch/LICENSE.md delete mode 100644 bitnami/rabbitmq-cluster-operator/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/rabbitmq-cluster-operator/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/rabbitmq-cluster-operator/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/rabbitmq-cluster-operator/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/rabbitmq-cluster-operator/.github/workflows/stale.yml delete mode 100644 bitnami/rabbitmq-cluster-operator/CODE_OF_CONDUCT.md delete mode 100644 bitnami/rabbitmq-cluster-operator/CONTRIBUTING.md delete mode 100644 bitnami/rabbitmq-cluster-operator/LICENSE.md delete mode 100644 bitnami/rabbitmq/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/rabbitmq/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/rabbitmq/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/rabbitmq/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/rabbitmq/.github/workflows/stale.yml delete mode 100644 bitnami/rabbitmq/CODE_OF_CONDUCT.md delete mode 100644 bitnami/rabbitmq/CONTRIBUTING.md delete mode 100644 bitnami/rabbitmq/LICENSE.md delete mode 100644 bitnami/rails/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/rails/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/rails/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/rails/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/rails/.github/workflows/stale.yml delete mode 100644 bitnami/rails/CODE_OF_CONDUCT.md delete mode 100644 bitnami/rails/CONTRIBUTING.md delete mode 100644 bitnami/rails/LICENSE.md delete mode 100644 bitnami/rclone/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/rclone/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/rclone/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/rclone/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/rclone/.github/workflows/stale.yml delete mode 100644 bitnami/rclone/CODE_OF_CONDUCT.md delete mode 100644 bitnami/rclone/CONTRIBUTING.md delete mode 100644 bitnami/rclone/LICENSE.md delete mode 100644 bitnami/redis-cluster/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/redis-cluster/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/redis-cluster/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/redis-cluster/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/redis-cluster/.github/workflows/stale.yml delete mode 100644 bitnami/redis-cluster/CODE_OF_CONDUCT.md delete mode 100644 bitnami/redis-cluster/CONTRIBUTING.md delete mode 100644 bitnami/redis-cluster/LICENSE.md delete mode 100644 bitnami/redis-exporter/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/redis-exporter/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/redis-exporter/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/redis-exporter/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/redis-exporter/.github/workflows/stale.yml delete mode 100644 bitnami/redis-exporter/CODE_OF_CONDUCT.md delete mode 100644 bitnami/redis-exporter/CONTRIBUTING.md delete mode 100644 bitnami/redis-exporter/LICENSE.md delete mode 100644 bitnami/redis-sentinel/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/redis-sentinel/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/redis-sentinel/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/redis-sentinel/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/redis-sentinel/.github/workflows/stale.yml delete mode 100644 bitnami/redis-sentinel/CODE_OF_CONDUCT.md delete mode 100644 bitnami/redis-sentinel/CONTRIBUTING.md delete mode 100644 bitnami/redis-sentinel/LICENSE.md delete mode 100644 bitnami/redis/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/redis/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/redis/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/redis/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/redis/.github/workflows/stale.yml delete mode 100644 bitnami/redis/CODE_OF_CONDUCT.md delete mode 100644 bitnami/redis/CONTRIBUTING.md delete mode 100644 bitnami/redis/LICENSE.md delete mode 100644 bitnami/redmine/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/redmine/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/redmine/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/redmine/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/redmine/.github/workflows/stale.yml delete mode 100644 bitnami/redmine/CODE_OF_CONDUCT.md delete mode 100644 bitnami/redmine/CONTRIBUTING.md delete mode 100644 bitnami/redmine/LICENSE.md delete mode 100644 bitnami/reportserver/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/reportserver/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/reportserver/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/reportserver/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/reportserver/.github/workflows/stale.yml delete mode 100644 bitnami/reportserver/CODE_OF_CONDUCT.md delete mode 100644 bitnami/reportserver/CONTRIBUTING.md delete mode 100644 bitnami/reportserver/LICENSE.md delete mode 100644 bitnami/reportserverenterprise/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/reportserverenterprise/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/reportserverenterprise/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/reportserverenterprise/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/reportserverenterprise/.github/workflows/stale.yml delete mode 100644 bitnami/reportserverenterprise/CODE_OF_CONDUCT.md delete mode 100644 bitnami/reportserverenterprise/CONTRIBUTING.md delete mode 100644 bitnami/reportserverenterprise/LICENSE.md delete mode 100644 bitnami/rmq-default-credential-updater/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/rmq-default-credential-updater/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/rmq-default-credential-updater/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/rmq-default-credential-updater/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/rmq-default-credential-updater/.github/workflows/stale.yml delete mode 100644 bitnami/rmq-default-credential-updater/CODE_OF_CONDUCT.md delete mode 100644 bitnami/rmq-default-credential-updater/CONTRIBUTING.md delete mode 100644 bitnami/rmq-default-credential-updater/LICENSE.md delete mode 100644 bitnami/rmq-messaging-topology-operator/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/rmq-messaging-topology-operator/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/rmq-messaging-topology-operator/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/rmq-messaging-topology-operator/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/rmq-messaging-topology-operator/.github/workflows/stale.yml delete mode 100644 bitnami/rmq-messaging-topology-operator/CODE_OF_CONDUCT.md delete mode 100644 bitnami/rmq-messaging-topology-operator/CONTRIBUTING.md delete mode 100644 bitnami/rmq-messaging-topology-operator/LICENSE.md delete mode 100644 bitnami/ruby/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/ruby/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/ruby/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/ruby/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/ruby/.github/workflows/stale.yml delete mode 100644 bitnami/ruby/CODE_OF_CONDUCT.md delete mode 100644 bitnami/ruby/CONTRIBUTING.md delete mode 100644 bitnami/ruby/LICENSE.md delete mode 100644 bitnami/service-catalog/.github/ISSUE_TEMPLATE.md delete mode 100644 bitnami/service-catalog/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/service-catalog/.github/workflows/stale.yml delete mode 100644 bitnami/service-catalog/CODE_OF_CONDUCT.md delete mode 100644 bitnami/service-catalog/CONTRIBUTING.md delete mode 100644 bitnami/service-catalog/LICENSE.md delete mode 100644 bitnami/solr/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/solr/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/solr/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/solr/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/solr/.github/workflows/stale.yml delete mode 100644 bitnami/solr/CODE_OF_CONDUCT.md delete mode 100644 bitnami/solr/CONTRIBUTING.md delete mode 100644 bitnami/solr/LICENSE.md delete mode 100644 bitnami/sonarqube/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/sonarqube/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/sonarqube/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/sonarqube/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/sonarqube/.github/workflows/stale.yml delete mode 100644 bitnami/sonarqube/CODE_OF_CONDUCT.md delete mode 100644 bitnami/sonarqube/CONTRIBUTING.md delete mode 100644 bitnami/sonarqube/LICENSE.md delete mode 100644 bitnami/spark/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/spark/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/spark/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/spark/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/spark/.github/workflows/stale.yml delete mode 100644 bitnami/spark/CODE_OF_CONDUCT.md delete mode 100644 bitnami/spark/CONTRIBUTING.md delete mode 100644 bitnami/spark/LICENSE.md delete mode 100644 bitnami/spring-cloud-dataflow-composed-task-runner/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/spring-cloud-dataflow-composed-task-runner/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/spring-cloud-dataflow-composed-task-runner/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/spring-cloud-dataflow-composed-task-runner/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/spring-cloud-dataflow-composed-task-runner/.github/workflows/stale.yml delete mode 100644 bitnami/spring-cloud-dataflow-composed-task-runner/CODE_OF_CONDUCT.md delete mode 100644 bitnami/spring-cloud-dataflow-composed-task-runner/CONTRIBUTING.md delete mode 100644 bitnami/spring-cloud-dataflow-composed-task-runner/LICENSE.md delete mode 100644 bitnami/spring-cloud-dataflow-shell/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/spring-cloud-dataflow-shell/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/spring-cloud-dataflow-shell/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/spring-cloud-dataflow-shell/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/spring-cloud-dataflow-shell/.github/workflows/stale.yml delete mode 100644 bitnami/spring-cloud-dataflow-shell/CODE_OF_CONDUCT.md delete mode 100644 bitnami/spring-cloud-dataflow-shell/CONTRIBUTING.md delete mode 100644 bitnami/spring-cloud-dataflow-shell/LICENSE.md delete mode 100644 bitnami/spring-cloud-dataflow/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/spring-cloud-dataflow/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/spring-cloud-dataflow/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/spring-cloud-dataflow/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/spring-cloud-dataflow/.github/workflows/stale.yml delete mode 100644 bitnami/spring-cloud-dataflow/CODE_OF_CONDUCT.md delete mode 100644 bitnami/spring-cloud-dataflow/CONTRIBUTING.md delete mode 100644 bitnami/spring-cloud-dataflow/LICENSE.md delete mode 100644 bitnami/spring-cloud-skipper-shell/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/spring-cloud-skipper-shell/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/spring-cloud-skipper-shell/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/spring-cloud-skipper-shell/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/spring-cloud-skipper-shell/.github/workflows/stale.yml delete mode 100644 bitnami/spring-cloud-skipper-shell/CODE_OF_CONDUCT.md delete mode 100644 bitnami/spring-cloud-skipper-shell/CONTRIBUTING.md delete mode 100644 bitnami/spring-cloud-skipper-shell/LICENSE.md delete mode 100644 bitnami/spring-cloud-skipper/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/spring-cloud-skipper/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/spring-cloud-skipper/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/spring-cloud-skipper/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/spring-cloud-skipper/.github/workflows/stale.yml delete mode 100644 bitnami/spring-cloud-skipper/CODE_OF_CONDUCT.md delete mode 100644 bitnami/spring-cloud-skipper/CONTRIBUTING.md delete mode 100644 bitnami/spring-cloud-skipper/LICENSE.md delete mode 100644 bitnami/suitecrm/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/suitecrm/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/suitecrm/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/suitecrm/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/suitecrm/.github/workflows/stale.yml delete mode 100644 bitnami/suitecrm/CODE_OF_CONDUCT.md delete mode 100644 bitnami/suitecrm/CONTRIBUTING.md delete mode 100644 bitnami/suitecrm/LICENSE.md delete mode 100644 bitnami/symfony/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/symfony/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/symfony/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/symfony/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/symfony/.github/workflows/stale.yml delete mode 100644 bitnami/symfony/CODE_OF_CONDUCT.md delete mode 100644 bitnami/symfony/CONTRIBUTING.md delete mode 100644 bitnami/symfony/LICENSE.md delete mode 100644 bitnami/telegraf/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/telegraf/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/telegraf/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/telegraf/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/telegraf/.github/workflows/stale.yml delete mode 100644 bitnami/telegraf/CODE_OF_CONDUCT.md delete mode 100644 bitnami/telegraf/CONTRIBUTING.md delete mode 100644 bitnami/telegraf/LICENSE.md delete mode 100644 bitnami/tensorflow-intel/.github/ISSUE_TEMPLATE.md delete mode 100644 bitnami/tensorflow-intel/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/tensorflow-intel/.github/workflows/stale.yml delete mode 100644 bitnami/tensorflow-intel/CODE_OF_CONDUCT.md delete mode 100644 bitnami/tensorflow-intel/CONTRIBUTING.md delete mode 100644 bitnami/tensorflow-intel/LICENSE.md delete mode 100644 bitnami/tensorflow-resnet/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/tensorflow-resnet/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/tensorflow-resnet/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/tensorflow-resnet/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/tensorflow-resnet/.github/workflows/stale.yml delete mode 100644 bitnami/tensorflow-resnet/CODE_OF_CONDUCT.md delete mode 100644 bitnami/tensorflow-resnet/CONTRIBUTING.md delete mode 100644 bitnami/tensorflow-resnet/LICENSE.md delete mode 100644 bitnami/tensorflow-serving/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/tensorflow-serving/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/tensorflow-serving/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/tensorflow-serving/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/tensorflow-serving/.github/workflows/stale.yml delete mode 100644 bitnami/tensorflow-serving/CODE_OF_CONDUCT.md delete mode 100644 bitnami/tensorflow-serving/CONTRIBUTING.md delete mode 100644 bitnami/tensorflow-serving/LICENSE.md delete mode 100644 bitnami/testlink/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/testlink/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/testlink/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/testlink/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/testlink/.github/workflows/stale.yml delete mode 100644 bitnami/testlink/CODE_OF_CONDUCT.md delete mode 100644 bitnami/testlink/CONTRIBUTING.md delete mode 100644 bitnami/testlink/LICENSE.md delete mode 100644 bitnami/tests/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/tests/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/tests/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/tests/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/tests/.github/workflows/stale.yml delete mode 100644 bitnami/tests/CODE_OF_CONDUCT.md delete mode 100644 bitnami/tests/CONTRIBUTING.md delete mode 100644 bitnami/tests/LICENSE.md delete mode 100644 bitnami/thanos/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/thanos/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/thanos/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/thanos/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/thanos/.github/workflows/stale.yml delete mode 100644 bitnami/thanos/CODE_OF_CONDUCT.md delete mode 100644 bitnami/thanos/CONTRIBUTING.md delete mode 100644 bitnami/thanos/LICENSE.md delete mode 100644 bitnami/tomcat/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/tomcat/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/tomcat/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/tomcat/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/tomcat/.github/workflows/stale.yml delete mode 100644 bitnami/tomcat/CODE_OF_CONDUCT.md delete mode 100644 bitnami/tomcat/CONTRIBUTING.md delete mode 100644 bitnami/tomcat/LICENSE.md delete mode 100644 bitnami/trivy/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/trivy/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/trivy/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/trivy/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/trivy/.github/workflows/stale.yml delete mode 100644 bitnami/trivy/CODE_OF_CONDUCT.md delete mode 100644 bitnami/trivy/CONTRIBUTING.md delete mode 100644 bitnami/trivy/LICENSE.md delete mode 100644 bitnami/user-broker/.github/ISSUE_TEMPLATE.md delete mode 100644 bitnami/user-broker/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/user-broker/.github/workflows/stale.yml delete mode 100644 bitnami/user-broker/CODE_OF_CONDUCT.md delete mode 100644 bitnami/user-broker/CONTRIBUTING.md delete mode 100644 bitnami/user-broker/LICENSE.md delete mode 100644 bitnami/wal-g/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/wal-g/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/wal-g/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/wal-g/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/wal-g/.github/workflows/stale.yml delete mode 100644 bitnami/wal-g/CODE_OF_CONDUCT.md delete mode 100644 bitnami/wal-g/CONTRIBUTING.md delete mode 100644 bitnami/wal-g/LICENSE.md delete mode 100644 bitnami/wavefront-adapter-for-istio/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/wavefront-adapter-for-istio/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/wavefront-adapter-for-istio/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/wavefront-adapter-for-istio/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/wavefront-adapter-for-istio/.github/workflows/stale.yml delete mode 100644 bitnami/wavefront-adapter-for-istio/CODE_OF_CONDUCT.md delete mode 100644 bitnami/wavefront-adapter-for-istio/CONTRIBUTING.md delete mode 100644 bitnami/wavefront-adapter-for-istio/LICENSE.md delete mode 100644 bitnami/wavefront-hpa-adapter/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/wavefront-hpa-adapter/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/wavefront-hpa-adapter/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/wavefront-hpa-adapter/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/wavefront-hpa-adapter/.github/workflows/stale.yml delete mode 100644 bitnami/wavefront-hpa-adapter/CODE_OF_CONDUCT.md delete mode 100644 bitnami/wavefront-hpa-adapter/CONTRIBUTING.md delete mode 100644 bitnami/wavefront-hpa-adapter/LICENSE.md delete mode 100644 bitnami/wavefront-kubernetes-collector/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/wavefront-kubernetes-collector/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/wavefront-kubernetes-collector/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/wavefront-kubernetes-collector/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/wavefront-kubernetes-collector/.github/workflows/stale.yml delete mode 100644 bitnami/wavefront-kubernetes-collector/CODE_OF_CONDUCT.md delete mode 100644 bitnami/wavefront-kubernetes-collector/CONTRIBUTING.md delete mode 100644 bitnami/wavefront-kubernetes-collector/LICENSE.md delete mode 100644 bitnami/wavefront-prometheus-storage-adapter/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/wavefront-prometheus-storage-adapter/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/wavefront-prometheus-storage-adapter/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/wavefront-prometheus-storage-adapter/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/wavefront-prometheus-storage-adapter/.github/workflows/stale.yml delete mode 100644 bitnami/wavefront-prometheus-storage-adapter/CODE_OF_CONDUCT.md delete mode 100644 bitnami/wavefront-prometheus-storage-adapter/CONTRIBUTING.md delete mode 100644 bitnami/wavefront-prometheus-storage-adapter/LICENSE.md delete mode 100644 bitnami/wavefront-proxy/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/wavefront-proxy/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/wavefront-proxy/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/wavefront-proxy/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/wavefront-proxy/.github/workflows/stale.yml delete mode 100644 bitnami/wavefront-proxy/CODE_OF_CONDUCT.md delete mode 100644 bitnami/wavefront-proxy/CONTRIBUTING.md delete mode 100644 bitnami/wavefront-proxy/LICENSE.md delete mode 100644 bitnami/wildfly/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/wildfly/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/wildfly/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/wildfly/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/wildfly/.github/workflows/stale.yml delete mode 100644 bitnami/wildfly/CODE_OF_CONDUCT.md delete mode 100644 bitnami/wildfly/CONTRIBUTING.md delete mode 100644 bitnami/wildfly/LICENSE.md delete mode 100644 bitnami/wordpress-intel/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/wordpress-intel/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/wordpress-intel/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/wordpress-intel/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/wordpress-intel/.github/workflows/stale.yml delete mode 100644 bitnami/wordpress-intel/CODE_OF_CONDUCT.md delete mode 100644 bitnami/wordpress-intel/CONTRIBUTING.md delete mode 100644 bitnami/wordpress-intel/LICENSE.md delete mode 100644 bitnami/wordpress-nginx/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/wordpress-nginx/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/wordpress-nginx/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/wordpress-nginx/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/wordpress-nginx/.github/workflows/stale.yml delete mode 100644 bitnami/wordpress-nginx/CODE_OF_CONDUCT.md delete mode 100644 bitnami/wordpress-nginx/CONTRIBUTING.md delete mode 100644 bitnami/wordpress-nginx/LICENSE.md delete mode 100644 bitnami/wordpress/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/wordpress/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/wordpress/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/wordpress/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/wordpress/.github/workflows/stale.yml delete mode 100644 bitnami/wordpress/CODE_OF_CONDUCT.md delete mode 100644 bitnami/wordpress/CONTRIBUTING.md delete mode 100644 bitnami/wordpress/LICENSE.md delete mode 100644 bitnami/zookeeper/.github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 bitnami/zookeeper/.github/ISSUE_TEMPLATE/config.yml delete mode 100644 bitnami/zookeeper/.github/ISSUE_TEMPLATE/feature_request.yml delete mode 100644 bitnami/zookeeper/.github/PULL_REQUEST_TEMPLATE.md delete mode 100644 bitnami/zookeeper/.github/workflows/stale.yml delete mode 100644 bitnami/zookeeper/CODE_OF_CONDUCT.md delete mode 100644 bitnami/zookeeper/CONTRIBUTING.md delete mode 100644 bitnami/zookeeper/LICENSE.md create mode 100644 scripts/fetch-commits.sh diff --git a/bitnami/acmesolver/.github/ISSUE_TEMPLATE/bug_report.yml b/.github/ISSUE_TEMPLATE/bug_report.yml similarity index 100% rename from bitnami/acmesolver/.github/ISSUE_TEMPLATE/bug_report.yml rename to .github/ISSUE_TEMPLATE/bug_report.yml diff --git a/bitnami/acmesolver/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml similarity index 100% rename from bitnami/acmesolver/.github/ISSUE_TEMPLATE/config.yml rename to .github/ISSUE_TEMPLATE/config.yml diff --git a/bitnami/acmesolver/.github/ISSUE_TEMPLATE/feature_request.yml b/.github/ISSUE_TEMPLATE/feature_request.yml similarity index 100% rename from bitnami/acmesolver/.github/ISSUE_TEMPLATE/feature_request.yml rename to .github/ISSUE_TEMPLATE/feature_request.yml diff --git a/bitnami/acmesolver/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md similarity index 100% rename from bitnami/acmesolver/.github/PULL_REQUEST_TEMPLATE.md rename to .github/PULL_REQUEST_TEMPLATE.md diff --git a/bitnami/acmesolver/.github/workflows/stale.yml b/.github/workflows/stale.yml similarity index 100% rename from bitnami/acmesolver/.github/workflows/stale.yml rename to .github/workflows/stale.yml diff --git a/.github/workflows/sync.yaml b/.github/workflows/sync.yaml new file mode 100644 index 000000000000..5f10f38586b3 --- /dev/null +++ b/.github/workflows/sync.yaml @@ -0,0 +1,17 @@ +name: Sync containers repositories + +on: + schedule: + # Every day at 1 AM + - cron: '0 1 * * *' +jobs: + build: + name: Trigger Site Rebuild + runs-on: ubuntu-latest + steps: + - name: Checkout bitnami/containers + uses: actions/checkout@v2 + with: + token: ${{ secrets.BITNAMI_BOT_SECRET }} + - name: Fetch + run: ./scripts/fetch-commits.sh diff --git a/README.md b/README.md index aeb0cd88b2f1..bc54667f9fdd 100644 --- a/README.md +++ b/README.md @@ -1 +1,4 @@ # Bitnami Containers + +> NOTE: We use the latest commit to know the missing ones to sync. Do not edit this repository manually or the sync will be broken. +> If you edit this repo please take care of scifying how many commits you added into the `COMMIT_SHIFT` env var when calling the `fetch-commits.sh` script diff --git a/bitnami/acmesolver/CODE_OF_CONDUCT.md b/bitnami/acmesolver/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/acmesolver/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/acmesolver/CONTRIBUTING.md b/bitnami/acmesolver/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/acmesolver/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/acmesolver/LICENSE.md b/bitnami/acmesolver/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/acmesolver/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/airflow-exporter/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/airflow-exporter/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/airflow-exporter/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/airflow-exporter/.github/ISSUE_TEMPLATE/config.yml b/bitnami/airflow-exporter/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/airflow-exporter/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/airflow-exporter/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/airflow-exporter/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/airflow-exporter/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/airflow-exporter/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/airflow-exporter/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/airflow-exporter/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/airflow-exporter/.github/workflows/stale.yml b/bitnami/airflow-exporter/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/airflow-exporter/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/airflow-exporter/CODE_OF_CONDUCT.md b/bitnami/airflow-exporter/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/airflow-exporter/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/airflow-exporter/CONTRIBUTING.md b/bitnami/airflow-exporter/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/airflow-exporter/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/airflow-exporter/LICENSE.md b/bitnami/airflow-exporter/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/airflow-exporter/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/airflow-scheduler/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/airflow-scheduler/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/airflow-scheduler/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/airflow-scheduler/.github/ISSUE_TEMPLATE/config.yml b/bitnami/airflow-scheduler/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/airflow-scheduler/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/airflow-scheduler/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/airflow-scheduler/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/airflow-scheduler/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/airflow-scheduler/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/airflow-scheduler/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/airflow-scheduler/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/airflow-scheduler/.github/workflows/stale.yml b/bitnami/airflow-scheduler/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/airflow-scheduler/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/airflow-scheduler/CODE_OF_CONDUCT.md b/bitnami/airflow-scheduler/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/airflow-scheduler/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/airflow-scheduler/CONTRIBUTING.md b/bitnami/airflow-scheduler/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/airflow-scheduler/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/airflow-scheduler/LICENSE.md b/bitnami/airflow-scheduler/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/airflow-scheduler/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/airflow-worker/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/airflow-worker/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/airflow-worker/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/airflow-worker/.github/ISSUE_TEMPLATE/config.yml b/bitnami/airflow-worker/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/airflow-worker/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/airflow-worker/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/airflow-worker/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/airflow-worker/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/airflow-worker/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/airflow-worker/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/airflow-worker/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/airflow-worker/.github/workflows/stale.yml b/bitnami/airflow-worker/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/airflow-worker/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/airflow-worker/CODE_OF_CONDUCT.md b/bitnami/airflow-worker/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/airflow-worker/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/airflow-worker/CONTRIBUTING.md b/bitnami/airflow-worker/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/airflow-worker/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/airflow-worker/LICENSE.md b/bitnami/airflow-worker/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/airflow-worker/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/airflow/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/airflow/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/airflow/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/airflow/.github/ISSUE_TEMPLATE/config.yml b/bitnami/airflow/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/airflow/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/airflow/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/airflow/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/airflow/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/airflow/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/airflow/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/airflow/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/airflow/.github/workflows/stale.yml b/bitnami/airflow/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/airflow/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/airflow/CODE_OF_CONDUCT.md b/bitnami/airflow/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/airflow/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/airflow/CONTRIBUTING.md b/bitnami/airflow/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/airflow/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/airflow/LICENSE.md b/bitnami/airflow/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/airflow/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/alertmanager/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/alertmanager/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/alertmanager/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/alertmanager/.github/ISSUE_TEMPLATE/config.yml b/bitnami/alertmanager/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/alertmanager/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/alertmanager/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/alertmanager/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/alertmanager/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/alertmanager/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/alertmanager/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/alertmanager/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/alertmanager/.github/workflows/stale.yml b/bitnami/alertmanager/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/alertmanager/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/alertmanager/CODE_OF_CONDUCT.md b/bitnami/alertmanager/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/alertmanager/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/alertmanager/CONTRIBUTING.md b/bitnami/alertmanager/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/alertmanager/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/alertmanager/LICENSE.md b/bitnami/alertmanager/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/alertmanager/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/apache-exporter/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/apache-exporter/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/apache-exporter/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/apache-exporter/.github/ISSUE_TEMPLATE/config.yml b/bitnami/apache-exporter/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/apache-exporter/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/apache-exporter/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/apache-exporter/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/apache-exporter/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/apache-exporter/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/apache-exporter/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/apache-exporter/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/apache-exporter/.github/workflows/stale.yml b/bitnami/apache-exporter/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/apache-exporter/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/apache-exporter/CODE_OF_CONDUCT.md b/bitnami/apache-exporter/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/apache-exporter/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/apache-exporter/CONTRIBUTING.md b/bitnami/apache-exporter/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/apache-exporter/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/apache-exporter/LICENSE.md b/bitnami/apache-exporter/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/apache-exporter/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/apache/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/apache/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/apache/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/apache/.github/ISSUE_TEMPLATE/config.yml b/bitnami/apache/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/apache/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/apache/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/apache/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/apache/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/apache/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/apache/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/apache/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/apache/.github/workflows/stale.yml b/bitnami/apache/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/apache/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/apache/CODE_OF_CONDUCT.md b/bitnami/apache/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/apache/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/apache/CONTRIBUTING.md b/bitnami/apache/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/apache/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/apache/LICENSE.md b/bitnami/apache/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/apache/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/argo-cd/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/argo-cd/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/argo-cd/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/argo-cd/.github/ISSUE_TEMPLATE/config.yml b/bitnami/argo-cd/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/argo-cd/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/argo-cd/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/argo-cd/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/argo-cd/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/argo-cd/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/argo-cd/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/argo-cd/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/argo-cd/.github/workflows/stale.yml b/bitnami/argo-cd/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/argo-cd/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/argo-cd/CODE_OF_CONDUCT.md b/bitnami/argo-cd/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/argo-cd/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/argo-cd/CONTRIBUTING.md b/bitnami/argo-cd/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/argo-cd/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/argo-cd/LICENSE.md b/bitnami/argo-cd/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/argo-cd/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/argo-workflow-cli/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/argo-workflow-cli/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/argo-workflow-cli/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/argo-workflow-cli/.github/ISSUE_TEMPLATE/config.yml b/bitnami/argo-workflow-cli/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/argo-workflow-cli/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/argo-workflow-cli/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/argo-workflow-cli/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/argo-workflow-cli/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/argo-workflow-cli/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/argo-workflow-cli/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/argo-workflow-cli/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/argo-workflow-cli/.github/workflows/stale.yml b/bitnami/argo-workflow-cli/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/argo-workflow-cli/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/argo-workflow-cli/CODE_OF_CONDUCT.md b/bitnami/argo-workflow-cli/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/argo-workflow-cli/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/argo-workflow-cli/CONTRIBUTING.md b/bitnami/argo-workflow-cli/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/argo-workflow-cli/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/argo-workflow-cli/LICENSE.md b/bitnami/argo-workflow-cli/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/argo-workflow-cli/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/argo-workflow-controller/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/argo-workflow-controller/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/argo-workflow-controller/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/argo-workflow-controller/.github/ISSUE_TEMPLATE/config.yml b/bitnami/argo-workflow-controller/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/argo-workflow-controller/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/argo-workflow-controller/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/argo-workflow-controller/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/argo-workflow-controller/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/argo-workflow-controller/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/argo-workflow-controller/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/argo-workflow-controller/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/argo-workflow-controller/.github/workflows/stale.yml b/bitnami/argo-workflow-controller/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/argo-workflow-controller/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/argo-workflow-controller/CODE_OF_CONDUCT.md b/bitnami/argo-workflow-controller/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/argo-workflow-controller/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/argo-workflow-controller/CONTRIBUTING.md b/bitnami/argo-workflow-controller/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/argo-workflow-controller/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/argo-workflow-controller/LICENSE.md b/bitnami/argo-workflow-controller/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/argo-workflow-controller/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/argo-workflow-exec/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/argo-workflow-exec/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/argo-workflow-exec/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/argo-workflow-exec/.github/ISSUE_TEMPLATE/config.yml b/bitnami/argo-workflow-exec/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/argo-workflow-exec/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/argo-workflow-exec/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/argo-workflow-exec/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/argo-workflow-exec/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/argo-workflow-exec/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/argo-workflow-exec/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/argo-workflow-exec/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/argo-workflow-exec/.github/workflows/stale.yml b/bitnami/argo-workflow-exec/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/argo-workflow-exec/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/argo-workflow-exec/CODE_OF_CONDUCT.md b/bitnami/argo-workflow-exec/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/argo-workflow-exec/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/argo-workflow-exec/CONTRIBUTING.md b/bitnami/argo-workflow-exec/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/argo-workflow-exec/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/argo-workflow-exec/LICENSE.md b/bitnami/argo-workflow-exec/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/argo-workflow-exec/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/aspnet-core/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/aspnet-core/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/aspnet-core/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/aspnet-core/.github/ISSUE_TEMPLATE/config.yml b/bitnami/aspnet-core/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/aspnet-core/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/aspnet-core/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/aspnet-core/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/aspnet-core/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/aspnet-core/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/aspnet-core/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/aspnet-core/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/aspnet-core/.github/workflows/stale.yml b/bitnami/aspnet-core/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/aspnet-core/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/aspnet-core/CODE_OF_CONDUCT.md b/bitnami/aspnet-core/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/aspnet-core/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/aspnet-core/CONTRIBUTING.md b/bitnami/aspnet-core/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/aspnet-core/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/aspnet-core/LICENSE.md b/bitnami/aspnet-core/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/aspnet-core/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/aws-cli/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/aws-cli/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/aws-cli/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/aws-cli/.github/ISSUE_TEMPLATE/config.yml b/bitnami/aws-cli/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/aws-cli/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/aws-cli/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/aws-cli/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/aws-cli/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/aws-cli/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/aws-cli/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/aws-cli/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/aws-cli/.github/workflows/stale.yml b/bitnami/aws-cli/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/aws-cli/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/aws-cli/CODE_OF_CONDUCT.md b/bitnami/aws-cli/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/aws-cli/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/aws-cli/CONTRIBUTING.md b/bitnami/aws-cli/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/aws-cli/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/aws-cli/LICENSE.md b/bitnami/aws-cli/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/aws-cli/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/azure-cli/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/azure-cli/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/azure-cli/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/azure-cli/.github/ISSUE_TEMPLATE/config.yml b/bitnami/azure-cli/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/azure-cli/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/azure-cli/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/azure-cli/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/azure-cli/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/azure-cli/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/azure-cli/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/azure-cli/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/azure-cli/.github/workflows/stale.yml b/bitnami/azure-cli/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/azure-cli/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/azure-cli/CODE_OF_CONDUCT.md b/bitnami/azure-cli/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/azure-cli/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/azure-cli/CONTRIBUTING.md b/bitnami/azure-cli/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/azure-cli/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/azure-cli/LICENSE.md b/bitnami/azure-cli/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/azure-cli/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/bitnami-shell/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/bitnami-shell/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/bitnami-shell/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/bitnami-shell/.github/ISSUE_TEMPLATE/config.yml b/bitnami/bitnami-shell/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/bitnami-shell/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/bitnami-shell/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/bitnami-shell/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/bitnami-shell/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/bitnami-shell/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/bitnami-shell/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/bitnami-shell/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/bitnami-shell/.github/workflows/stale.yml b/bitnami/bitnami-shell/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/bitnami-shell/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/bitnami-shell/CODE_OF_CONDUCT.md b/bitnami/bitnami-shell/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/bitnami-shell/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/bitnami-shell/CONTRIBUTING.md b/bitnami/bitnami-shell/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/bitnami-shell/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/bitnami-shell/LICENSE.md b/bitnami/bitnami-shell/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/bitnami-shell/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/blackbox-exporter/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/blackbox-exporter/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/blackbox-exporter/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/blackbox-exporter/.github/ISSUE_TEMPLATE/config.yml b/bitnami/blackbox-exporter/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/blackbox-exporter/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/blackbox-exporter/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/blackbox-exporter/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/blackbox-exporter/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/blackbox-exporter/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/blackbox-exporter/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/blackbox-exporter/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/blackbox-exporter/.github/workflows/stale.yml b/bitnami/blackbox-exporter/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/blackbox-exporter/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/blackbox-exporter/CODE_OF_CONDUCT.md b/bitnami/blackbox-exporter/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/blackbox-exporter/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/blackbox-exporter/CONTRIBUTING.md b/bitnami/blackbox-exporter/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/blackbox-exporter/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/blackbox-exporter/LICENSE.md b/bitnami/blackbox-exporter/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/blackbox-exporter/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/cainjector/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/cainjector/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/cainjector/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/cainjector/.github/ISSUE_TEMPLATE/config.yml b/bitnami/cainjector/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/cainjector/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/cainjector/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/cainjector/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/cainjector/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/cainjector/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/cainjector/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/cainjector/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/cainjector/.github/workflows/stale.yml b/bitnami/cainjector/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/cainjector/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/cainjector/CODE_OF_CONDUCT.md b/bitnami/cainjector/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/cainjector/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/cainjector/CONTRIBUTING.md b/bitnami/cainjector/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/cainjector/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/cainjector/LICENSE.md b/bitnami/cainjector/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/cainjector/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/cassandra-exporter/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/cassandra-exporter/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/cassandra-exporter/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/cassandra-exporter/.github/ISSUE_TEMPLATE/config.yml b/bitnami/cassandra-exporter/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/cassandra-exporter/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/cassandra-exporter/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/cassandra-exporter/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/cassandra-exporter/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/cassandra-exporter/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/cassandra-exporter/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/cassandra-exporter/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/cassandra-exporter/.github/workflows/stale.yml b/bitnami/cassandra-exporter/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/cassandra-exporter/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/cassandra-exporter/CODE_OF_CONDUCT.md b/bitnami/cassandra-exporter/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/cassandra-exporter/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/cassandra-exporter/CONTRIBUTING.md b/bitnami/cassandra-exporter/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/cassandra-exporter/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/cassandra-exporter/LICENSE.md b/bitnami/cassandra-exporter/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/cassandra-exporter/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/cassandra/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/cassandra/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/cassandra/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/cassandra/.github/ISSUE_TEMPLATE/config.yml b/bitnami/cassandra/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/cassandra/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/cassandra/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/cassandra/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/cassandra/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/cassandra/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/cassandra/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/cassandra/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/cassandra/.github/workflows/stale.yml b/bitnami/cassandra/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/cassandra/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/cassandra/CODE_OF_CONDUCT.md b/bitnami/cassandra/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/cassandra/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/cassandra/CONTRIBUTING.md b/bitnami/cassandra/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/cassandra/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/cassandra/LICENSE.md b/bitnami/cassandra/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/cassandra/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/cert-manager-webhook/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/cert-manager-webhook/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/cert-manager-webhook/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/cert-manager-webhook/.github/ISSUE_TEMPLATE/config.yml b/bitnami/cert-manager-webhook/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/cert-manager-webhook/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/cert-manager-webhook/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/cert-manager-webhook/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/cert-manager-webhook/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/cert-manager-webhook/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/cert-manager-webhook/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/cert-manager-webhook/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/cert-manager-webhook/.github/workflows/stale.yml b/bitnami/cert-manager-webhook/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/cert-manager-webhook/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/cert-manager-webhook/CODE_OF_CONDUCT.md b/bitnami/cert-manager-webhook/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/cert-manager-webhook/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/cert-manager-webhook/CONTRIBUTING.md b/bitnami/cert-manager-webhook/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/cert-manager-webhook/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/cert-manager-webhook/LICENSE.md b/bitnami/cert-manager-webhook/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/cert-manager-webhook/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/cert-manager/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/cert-manager/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/cert-manager/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/cert-manager/.github/ISSUE_TEMPLATE/config.yml b/bitnami/cert-manager/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/cert-manager/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/cert-manager/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/cert-manager/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/cert-manager/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/cert-manager/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/cert-manager/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/cert-manager/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/cert-manager/.github/workflows/stale.yml b/bitnami/cert-manager/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/cert-manager/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/cert-manager/CODE_OF_CONDUCT.md b/bitnami/cert-manager/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/cert-manager/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/cert-manager/CONTRIBUTING.md b/bitnami/cert-manager/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/cert-manager/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/cert-manager/LICENSE.md b/bitnami/cert-manager/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/cert-manager/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/chartmuseum/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/chartmuseum/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/chartmuseum/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/chartmuseum/.github/ISSUE_TEMPLATE/config.yml b/bitnami/chartmuseum/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/chartmuseum/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/chartmuseum/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/chartmuseum/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/chartmuseum/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/chartmuseum/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/chartmuseum/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/chartmuseum/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/chartmuseum/.github/workflows/stale.yml b/bitnami/chartmuseum/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/chartmuseum/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/chartmuseum/CODE_OF_CONDUCT.md b/bitnami/chartmuseum/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/chartmuseum/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/chartmuseum/CONTRIBUTING.md b/bitnami/chartmuseum/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/chartmuseum/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/chartmuseum/LICENSE.md b/bitnami/chartmuseum/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/chartmuseum/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/cluster-autoscaler/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/cluster-autoscaler/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/cluster-autoscaler/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/cluster-autoscaler/.github/ISSUE_TEMPLATE/config.yml b/bitnami/cluster-autoscaler/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/cluster-autoscaler/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/cluster-autoscaler/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/cluster-autoscaler/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/cluster-autoscaler/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/cluster-autoscaler/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/cluster-autoscaler/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/cluster-autoscaler/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/cluster-autoscaler/.github/workflows/stale.yml b/bitnami/cluster-autoscaler/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/cluster-autoscaler/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/cluster-autoscaler/CODE_OF_CONDUCT.md b/bitnami/cluster-autoscaler/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/cluster-autoscaler/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/cluster-autoscaler/CONTRIBUTING.md b/bitnami/cluster-autoscaler/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/cluster-autoscaler/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/cluster-autoscaler/LICENSE.md b/bitnami/cluster-autoscaler/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/cluster-autoscaler/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/codeigniter/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/codeigniter/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/codeigniter/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/codeigniter/.github/ISSUE_TEMPLATE/config.yml b/bitnami/codeigniter/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/codeigniter/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/codeigniter/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/codeigniter/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/codeigniter/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/codeigniter/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/codeigniter/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/codeigniter/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/codeigniter/.github/workflows/stale.yml b/bitnami/codeigniter/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/codeigniter/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/codeigniter/CODE_OF_CONDUCT.md b/bitnami/codeigniter/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/codeigniter/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/codeigniter/CONTRIBUTING.md b/bitnami/codeigniter/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/codeigniter/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/codeigniter/LICENSE.md b/bitnami/codeigniter/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/codeigniter/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/concourse/.github/bug_report.yml b/bitnami/concourse/.github/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/concourse/.github/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/concourse/.github/config.yml b/bitnami/concourse/.github/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/concourse/.github/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/concourse/.github/feature_request.yml b/bitnami/concourse/.github/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/concourse/.github/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/concourse/CONTRIBUTING.md b/bitnami/concourse/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/concourse/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/concourse/LICENSE.md b/bitnami/concourse/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/concourse/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/configmap-reload/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/configmap-reload/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/configmap-reload/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/configmap-reload/.github/ISSUE_TEMPLATE/config.yml b/bitnami/configmap-reload/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/configmap-reload/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/configmap-reload/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/configmap-reload/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/configmap-reload/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/configmap-reload/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/configmap-reload/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/configmap-reload/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/configmap-reload/.github/workflows/stale.yml b/bitnami/configmap-reload/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/configmap-reload/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/configmap-reload/CODE_OF_CONDUCT.md b/bitnami/configmap-reload/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/configmap-reload/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/configmap-reload/CONTRIBUTING.md b/bitnami/configmap-reload/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/configmap-reload/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/configmap-reload/LICENSE.md b/bitnami/configmap-reload/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/configmap-reload/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/configurable-http-proxy/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/configurable-http-proxy/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/configurable-http-proxy/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/configurable-http-proxy/.github/ISSUE_TEMPLATE/config.yml b/bitnami/configurable-http-proxy/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/configurable-http-proxy/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/configurable-http-proxy/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/configurable-http-proxy/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/configurable-http-proxy/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/configurable-http-proxy/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/configurable-http-proxy/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/configurable-http-proxy/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/configurable-http-proxy/.github/workflows/stale.yml b/bitnami/configurable-http-proxy/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/configurable-http-proxy/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/configurable-http-proxy/CODE_OF_CONDUCT.md b/bitnami/configurable-http-proxy/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/configurable-http-proxy/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/configurable-http-proxy/CONTRIBUTING.md b/bitnami/configurable-http-proxy/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/configurable-http-proxy/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/configurable-http-proxy/LICENSE.md b/bitnami/configurable-http-proxy/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/configurable-http-proxy/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/consul-exporter/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/consul-exporter/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/consul-exporter/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/consul-exporter/.github/ISSUE_TEMPLATE/config.yml b/bitnami/consul-exporter/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/consul-exporter/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/consul-exporter/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/consul-exporter/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/consul-exporter/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/consul-exporter/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/consul-exporter/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/consul-exporter/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/consul-exporter/.github/workflows/stale.yml b/bitnami/consul-exporter/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/consul-exporter/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/consul-exporter/CODE_OF_CONDUCT.md b/bitnami/consul-exporter/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/consul-exporter/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/consul-exporter/CONTRIBUTING.md b/bitnami/consul-exporter/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/consul-exporter/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/consul-exporter/LICENSE.md b/bitnami/consul-exporter/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/consul-exporter/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/consul/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/consul/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/consul/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/consul/.github/ISSUE_TEMPLATE/config.yml b/bitnami/consul/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/consul/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/consul/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/consul/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/consul/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/consul/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/consul/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/consul/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/consul/.github/workflows/stale.yml b/bitnami/consul/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/consul/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/consul/CODE_OF_CONDUCT.md b/bitnami/consul/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/consul/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/consul/CONTRIBUTING.md b/bitnami/consul/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/consul/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/consul/LICENSE.md b/bitnami/consul/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/consul/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/contour-operator/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/contour-operator/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/contour-operator/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/contour-operator/.github/ISSUE_TEMPLATE/config.yml b/bitnami/contour-operator/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/contour-operator/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/contour-operator/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/contour-operator/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/contour-operator/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/contour-operator/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/contour-operator/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/contour-operator/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/contour-operator/.github/workflows/stale.yml b/bitnami/contour-operator/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/contour-operator/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/contour-operator/CODE_OF_CONDUCT.md b/bitnami/contour-operator/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/contour-operator/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/contour-operator/CONTRIBUTING.md b/bitnami/contour-operator/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/contour-operator/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/contour-operator/LICENSE.md b/bitnami/contour-operator/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/contour-operator/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/contour/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/contour/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/contour/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/contour/.github/ISSUE_TEMPLATE/config.yml b/bitnami/contour/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/contour/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/contour/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/contour/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/contour/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/contour/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/contour/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/contour/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/contour/.github/workflows/stale.yml b/bitnami/contour/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/contour/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/contour/CODE_OF_CONDUCT.md b/bitnami/contour/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/contour/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/contour/CONTRIBUTING.md b/bitnami/contour/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/contour/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/contour/LICENSE.md b/bitnami/contour/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/contour/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/cosign/.github/ISSUE_TEMPLATE.md b/bitnami/cosign/.github/ISSUE_TEMPLATE.md deleted file mode 100644 index a7a1a6fc7a0f..000000000000 --- a/bitnami/cosign/.github/ISSUE_TEMPLATE.md +++ /dev/null @@ -1,21 +0,0 @@ -**Description** - - - -**Steps to reproduce the issue:** - -1. [First Step] -2. [Second Step] -3. [and so on...] - -**Describe the results you received:** - - - -**Describe the results you expected:** - - - -**Additional information you deem important (e.g. issue happens only occasionally, environment details, etc.):** - - diff --git a/bitnami/cosign/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/cosign/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/cosign/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/cosign/.github/workflows/stale.yml b/bitnami/cosign/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/cosign/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/cosign/CODE_OF_CONDUCT.md b/bitnami/cosign/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/cosign/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/cosign/CONTRIBUTING.md b/bitnami/cosign/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/cosign/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/cosign/LICENSE.md b/bitnami/cosign/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/cosign/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/couchdb/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/couchdb/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/couchdb/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/couchdb/.github/ISSUE_TEMPLATE/config.yml b/bitnami/couchdb/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/couchdb/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/couchdb/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/couchdb/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/couchdb/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/couchdb/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/couchdb/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/couchdb/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/couchdb/.github/workflows/stale.yml b/bitnami/couchdb/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/couchdb/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/couchdb/CODE_OF_CONDUCT.md b/bitnami/couchdb/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/couchdb/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/couchdb/CONTRIBUTING.md b/bitnami/couchdb/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/couchdb/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/couchdb/LICENSE.md b/bitnami/couchdb/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/couchdb/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/dataplatform-emitter/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/dataplatform-emitter/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/dataplatform-emitter/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/dataplatform-emitter/.github/ISSUE_TEMPLATE/config.yml b/bitnami/dataplatform-emitter/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/dataplatform-emitter/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/dataplatform-emitter/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/dataplatform-emitter/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/dataplatform-emitter/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/dataplatform-emitter/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/dataplatform-emitter/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/dataplatform-emitter/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/dataplatform-emitter/.github/workflows/stale.yml b/bitnami/dataplatform-emitter/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/dataplatform-emitter/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/dataplatform-emitter/CODE_OF_CONDUCT.md b/bitnami/dataplatform-emitter/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/dataplatform-emitter/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/dataplatform-emitter/CONTRIBUTING.md b/bitnami/dataplatform-emitter/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/dataplatform-emitter/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/dataplatform-emitter/LICENSE.md b/bitnami/dataplatform-emitter/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/dataplatform-emitter/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/dataplatform-exporter/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/dataplatform-exporter/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/dataplatform-exporter/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/dataplatform-exporter/.github/ISSUE_TEMPLATE/config.yml b/bitnami/dataplatform-exporter/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/dataplatform-exporter/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/dataplatform-exporter/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/dataplatform-exporter/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/dataplatform-exporter/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/dataplatform-exporter/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/dataplatform-exporter/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/dataplatform-exporter/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/dataplatform-exporter/.github/workflows/stale.yml b/bitnami/dataplatform-exporter/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/dataplatform-exporter/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/dataplatform-exporter/CODE_OF_CONDUCT.md b/bitnami/dataplatform-exporter/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/dataplatform-exporter/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/dataplatform-exporter/CONTRIBUTING.md b/bitnami/dataplatform-exporter/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/dataplatform-exporter/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/dataplatform-exporter/LICENSE.md b/bitnami/dataplatform-exporter/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/dataplatform-exporter/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/dex/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/dex/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/dex/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/dex/.github/ISSUE_TEMPLATE/config.yml b/bitnami/dex/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/dex/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/dex/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/dex/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/dex/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/dex/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/dex/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/dex/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/dex/.github/workflows/stale.yml b/bitnami/dex/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/dex/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/dex/CODE_OF_CONDUCT.md b/bitnami/dex/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/dex/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/dex/CONTRIBUTING.md b/bitnami/dex/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/dex/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/dex/LICENSE.md b/bitnami/dex/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/dex/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/discourse/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/discourse/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/discourse/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/discourse/.github/ISSUE_TEMPLATE/config.yml b/bitnami/discourse/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/discourse/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/discourse/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/discourse/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/discourse/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/discourse/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/discourse/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/discourse/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/discourse/.github/workflows/stale.yml b/bitnami/discourse/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/discourse/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/discourse/CODE_OF_CONDUCT.md b/bitnami/discourse/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/discourse/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/discourse/CONTRIBUTING.md b/bitnami/discourse/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/discourse/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/discourse/LICENSE.md b/bitnami/discourse/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/discourse/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/dokuwiki/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/dokuwiki/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/dokuwiki/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/dokuwiki/.github/ISSUE_TEMPLATE/config.yml b/bitnami/dokuwiki/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/dokuwiki/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/dokuwiki/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/dokuwiki/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/dokuwiki/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/dokuwiki/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/dokuwiki/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/dokuwiki/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/dokuwiki/.github/workflows/stale.yml b/bitnami/dokuwiki/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/dokuwiki/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/dokuwiki/CODE_OF_CONDUCT.md b/bitnami/dokuwiki/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/dokuwiki/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/dokuwiki/CONTRIBUTING.md b/bitnami/dokuwiki/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/dokuwiki/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/dokuwiki/LICENSE.md b/bitnami/dokuwiki/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/dokuwiki/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/dotnet-sdk/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/dotnet-sdk/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/dotnet-sdk/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/dotnet-sdk/.github/ISSUE_TEMPLATE/config.yml b/bitnami/dotnet-sdk/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/dotnet-sdk/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/dotnet-sdk/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/dotnet-sdk/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/dotnet-sdk/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/dotnet-sdk/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/dotnet-sdk/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/dotnet-sdk/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/dotnet-sdk/.github/workflows/stale.yml b/bitnami/dotnet-sdk/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/dotnet-sdk/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/dotnet-sdk/CODE_OF_CONDUCT.md b/bitnami/dotnet-sdk/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/dotnet-sdk/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/dotnet-sdk/CONTRIBUTING.md b/bitnami/dotnet-sdk/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/dotnet-sdk/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/dotnet-sdk/LICENSE.md b/bitnami/dotnet-sdk/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/dotnet-sdk/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/dotnet/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/dotnet/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/dotnet/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/dotnet/.github/ISSUE_TEMPLATE/config.yml b/bitnami/dotnet/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/dotnet/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/dotnet/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/dotnet/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/dotnet/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/dotnet/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/dotnet/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/dotnet/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/dotnet/.github/workflows/stale.yml b/bitnami/dotnet/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/dotnet/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/dotnet/CODE_OF_CONDUCT.md b/bitnami/dotnet/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/dotnet/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/dotnet/CONTRIBUTING.md b/bitnami/dotnet/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/dotnet/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/dotnet/LICENSE.md b/bitnami/dotnet/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/dotnet/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/dreamfactory/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/dreamfactory/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/dreamfactory/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/dreamfactory/.github/ISSUE_TEMPLATE/config.yml b/bitnami/dreamfactory/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/dreamfactory/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/dreamfactory/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/dreamfactory/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/dreamfactory/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/dreamfactory/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/dreamfactory/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/dreamfactory/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/dreamfactory/.github/workflows/stale.yml b/bitnami/dreamfactory/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/dreamfactory/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/dreamfactory/CODE_OF_CONDUCT.md b/bitnami/dreamfactory/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/dreamfactory/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/dreamfactory/CONTRIBUTING.md b/bitnami/dreamfactory/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/dreamfactory/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/dreamfactory/LICENSE.md b/bitnami/dreamfactory/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/dreamfactory/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/drupal-nginx/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/drupal-nginx/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/drupal-nginx/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/drupal-nginx/.github/ISSUE_TEMPLATE/config.yml b/bitnami/drupal-nginx/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/drupal-nginx/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/drupal-nginx/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/drupal-nginx/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/drupal-nginx/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/drupal-nginx/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/drupal-nginx/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/drupal-nginx/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/drupal-nginx/.github/workflows/stale.yml b/bitnami/drupal-nginx/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/drupal-nginx/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/drupal-nginx/CODE_OF_CONDUCT.md b/bitnami/drupal-nginx/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/drupal-nginx/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/drupal-nginx/CONTRIBUTING.md b/bitnami/drupal-nginx/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/drupal-nginx/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/drupal-nginx/LICENSE.md b/bitnami/drupal-nginx/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/drupal-nginx/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/drupal/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/drupal/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/drupal/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/drupal/.github/ISSUE_TEMPLATE/config.yml b/bitnami/drupal/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/drupal/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/drupal/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/drupal/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/drupal/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/drupal/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/drupal/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/drupal/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/drupal/.github/workflows/stale.yml b/bitnami/drupal/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/drupal/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/drupal/CODE_OF_CONDUCT.md b/bitnami/drupal/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/drupal/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/drupal/CONTRIBUTING.md b/bitnami/drupal/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/drupal/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/drupal/LICENSE.md b/bitnami/drupal/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/drupal/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/ejbca/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/ejbca/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/ejbca/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/ejbca/.github/ISSUE_TEMPLATE/config.yml b/bitnami/ejbca/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/ejbca/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/ejbca/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/ejbca/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/ejbca/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/ejbca/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/ejbca/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/ejbca/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/ejbca/.github/workflows/stale.yml b/bitnami/ejbca/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/ejbca/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/ejbca/CODE_OF_CONDUCT.md b/bitnami/ejbca/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/ejbca/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/ejbca/CONTRIBUTING.md b/bitnami/ejbca/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/ejbca/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/ejbca/LICENSE.md b/bitnami/ejbca/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/ejbca/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/elasticsearch-curator/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/elasticsearch-curator/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/elasticsearch-curator/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/elasticsearch-curator/.github/ISSUE_TEMPLATE/config.yml b/bitnami/elasticsearch-curator/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/elasticsearch-curator/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/elasticsearch-curator/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/elasticsearch-curator/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/elasticsearch-curator/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/elasticsearch-curator/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/elasticsearch-curator/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/elasticsearch-curator/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/elasticsearch-curator/.github/workflows/stale.yml b/bitnami/elasticsearch-curator/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/elasticsearch-curator/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/elasticsearch-curator/CODE_OF_CONDUCT.md b/bitnami/elasticsearch-curator/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/elasticsearch-curator/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/elasticsearch-curator/CONTRIBUTING.md b/bitnami/elasticsearch-curator/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/elasticsearch-curator/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/elasticsearch-curator/LICENSE.md b/bitnami/elasticsearch-curator/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/elasticsearch-curator/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/elasticsearch-exporter/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/elasticsearch-exporter/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/elasticsearch-exporter/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/elasticsearch-exporter/.github/ISSUE_TEMPLATE/config.yml b/bitnami/elasticsearch-exporter/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/elasticsearch-exporter/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/elasticsearch-exporter/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/elasticsearch-exporter/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/elasticsearch-exporter/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/elasticsearch-exporter/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/elasticsearch-exporter/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/elasticsearch-exporter/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/elasticsearch-exporter/.github/workflows/stale.yml b/bitnami/elasticsearch-exporter/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/elasticsearch-exporter/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/elasticsearch-exporter/CODE_OF_CONDUCT.md b/bitnami/elasticsearch-exporter/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/elasticsearch-exporter/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/elasticsearch-exporter/CONTRIBUTING.md b/bitnami/elasticsearch-exporter/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/elasticsearch-exporter/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/elasticsearch-exporter/LICENSE.md b/bitnami/elasticsearch-exporter/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/elasticsearch-exporter/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/elasticsearch/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/elasticsearch/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/elasticsearch/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/elasticsearch/.github/ISSUE_TEMPLATE/config.yml b/bitnami/elasticsearch/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/elasticsearch/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/elasticsearch/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/elasticsearch/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/elasticsearch/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/elasticsearch/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/elasticsearch/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/elasticsearch/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/elasticsearch/.github/workflows/stale.yml b/bitnami/elasticsearch/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/elasticsearch/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/elasticsearch/CODE_OF_CONDUCT.md b/bitnami/elasticsearch/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/elasticsearch/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/elasticsearch/CONTRIBUTING.md b/bitnami/elasticsearch/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/elasticsearch/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/elasticsearch/LICENSE.md b/bitnami/elasticsearch/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/elasticsearch/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/envoy/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/envoy/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/envoy/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/envoy/.github/ISSUE_TEMPLATE/config.yml b/bitnami/envoy/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/envoy/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/envoy/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/envoy/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/envoy/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/envoy/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/envoy/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/envoy/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/envoy/.github/workflows/stale.yml b/bitnami/envoy/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/envoy/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/envoy/CODE_OF_CONDUCT.md b/bitnami/envoy/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/envoy/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/envoy/CONTRIBUTING.md b/bitnami/envoy/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/envoy/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/envoy/LICENSE.md b/bitnami/envoy/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/envoy/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/etcd/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/etcd/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/etcd/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/etcd/.github/ISSUE_TEMPLATE/config.yml b/bitnami/etcd/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/etcd/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/etcd/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/etcd/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/etcd/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/etcd/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/etcd/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/etcd/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/etcd/.github/workflows/stale.yml b/bitnami/etcd/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/etcd/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/etcd/CODE_OF_CONDUCT.md b/bitnami/etcd/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/etcd/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/etcd/CONTRIBUTING.md b/bitnami/etcd/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/etcd/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/etcd/LICENSE.md b/bitnami/etcd/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/etcd/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/express/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/express/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/express/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/express/.github/ISSUE_TEMPLATE/config.yml b/bitnami/express/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/express/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/express/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/express/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/express/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/express/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/express/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/express/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/express/.github/workflows/stale.yml b/bitnami/express/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/express/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/express/CODE_OF_CONDUCT.md b/bitnami/express/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/express/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/express/CONTRIBUTING.md b/bitnami/express/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/express/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/express/LICENSE.md b/bitnami/express/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/express/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/external-dns/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/external-dns/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/external-dns/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/external-dns/.github/ISSUE_TEMPLATE/config.yml b/bitnami/external-dns/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/external-dns/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/external-dns/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/external-dns/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/external-dns/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/external-dns/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/external-dns/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/external-dns/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/external-dns/.github/workflows/stale.yml b/bitnami/external-dns/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/external-dns/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/external-dns/CODE_OF_CONDUCT.md b/bitnami/external-dns/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/external-dns/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/external-dns/CONTRIBUTING.md b/bitnami/external-dns/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/external-dns/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/external-dns/LICENSE.md b/bitnami/external-dns/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/external-dns/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/fluent-bit/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/fluent-bit/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/fluent-bit/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/fluent-bit/.github/ISSUE_TEMPLATE/config.yml b/bitnami/fluent-bit/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/fluent-bit/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/fluent-bit/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/fluent-bit/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/fluent-bit/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/fluent-bit/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/fluent-bit/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/fluent-bit/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/fluent-bit/.github/workflows/stale.yml b/bitnami/fluent-bit/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/fluent-bit/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/fluent-bit/CODE_OF_CONDUCT.md b/bitnami/fluent-bit/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/fluent-bit/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/fluent-bit/CONTRIBUTING.md b/bitnami/fluent-bit/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/fluent-bit/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/fluent-bit/LICENSE.md b/bitnami/fluent-bit/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/fluent-bit/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/fluentd-exporter/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/fluentd-exporter/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/fluentd-exporter/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/fluentd-exporter/.github/ISSUE_TEMPLATE/config.yml b/bitnami/fluentd-exporter/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/fluentd-exporter/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/fluentd-exporter/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/fluentd-exporter/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/fluentd-exporter/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/fluentd-exporter/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/fluentd-exporter/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/fluentd-exporter/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/fluentd-exporter/.github/workflows/stale.yml b/bitnami/fluentd-exporter/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/fluentd-exporter/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/fluentd-exporter/CODE_OF_CONDUCT.md b/bitnami/fluentd-exporter/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/fluentd-exporter/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/fluentd-exporter/CONTRIBUTING.md b/bitnami/fluentd-exporter/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/fluentd-exporter/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/fluentd-exporter/LICENSE.md b/bitnami/fluentd-exporter/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/fluentd-exporter/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/fluentd/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/fluentd/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/fluentd/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/fluentd/.github/ISSUE_TEMPLATE/config.yml b/bitnami/fluentd/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/fluentd/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/fluentd/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/fluentd/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/fluentd/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/fluentd/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/fluentd/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/fluentd/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/fluentd/.github/workflows/stale.yml b/bitnami/fluentd/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/fluentd/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/fluentd/CODE_OF_CONDUCT.md b/bitnami/fluentd/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/fluentd/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/fluentd/CONTRIBUTING.md b/bitnami/fluentd/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/fluentd/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/fluentd/LICENSE.md b/bitnami/fluentd/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/fluentd/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/geode/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/geode/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/geode/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/geode/.github/ISSUE_TEMPLATE/config.yml b/bitnami/geode/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/geode/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/geode/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/geode/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/geode/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/geode/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/geode/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/geode/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/geode/.github/stale.yml b/bitnami/geode/.github/stale.yml deleted file mode 100644 index ea65d3277a62..000000000000 --- a/bitnami/geode/.github/stale.yml +++ /dev/null @@ -1,36 +0,0 @@ -# Configuration for probot-stale - https://github.com/probot/stale - -# Number of days of inactivity before an Issue or Pull Request becomes stale -daysUntilStale: 15 - -# Number of days of inactivity before a stale Issue or Pull Request is closed. -daysUntilClose: 5 - -# Issues or Pull Requests with these labels will never be considered stale. Set to `[]` to disable -exemptLabels: - - on-hold - -# Label to use when marking as stale -staleLabel: stale - -issues: - # Comment to post when marking as stale. Set to `false` to disable - markComment: > - This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback. - - # Comment to post when closing a stale Issue or Pull Request. - closeComment: > - Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary. - -pulls: - # Comment to post when marking as stale. Set to `false` to disable - markComment: > - This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution. - - # Comment to post when closing a stale Issue or Pull Request. - closeComment: > - Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary. - -# Limit the number of actions per hour, from 1-30. Default is 30 -limitPerRun: 30 - diff --git a/bitnami/geode/.github/workflows/stale.yml b/bitnami/geode/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/geode/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/geode/CODE_OF_CONDUCT.md b/bitnami/geode/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/geode/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/geode/CONTRIBUTING.md b/bitnami/geode/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/geode/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/geode/LICENSE.md b/bitnami/geode/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/geode/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/ghost/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/ghost/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/ghost/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/ghost/.github/ISSUE_TEMPLATE/config.yml b/bitnami/ghost/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/ghost/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/ghost/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/ghost/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/ghost/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/ghost/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/ghost/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/ghost/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/ghost/.github/workflows/stale.yml b/bitnami/ghost/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/ghost/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/ghost/CODE_OF_CONDUCT.md b/bitnami/ghost/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/ghost/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/ghost/CONTRIBUTING.md b/bitnami/ghost/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/ghost/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/ghost/LICENSE.md b/bitnami/ghost/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/ghost/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/git/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/git/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/git/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/git/.github/ISSUE_TEMPLATE/config.yml b/bitnami/git/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/git/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/git/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/git/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/git/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/git/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/git/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index a304c693d2bd..000000000000 --- a/bitnami/git/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,33 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - - diff --git a/bitnami/git/.github/workflows/stale.yml b/bitnami/git/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/git/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/git/CODE_OF_CONDUCT.md b/bitnami/git/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/git/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/git/CONTRIBUTING.md b/bitnami/git/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/git/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/git/LICENSE.md b/bitnami/git/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/git/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/gitlab-runner-helper/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/gitlab-runner-helper/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/gitlab-runner-helper/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/gitlab-runner-helper/.github/ISSUE_TEMPLATE/config.yml b/bitnami/gitlab-runner-helper/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/gitlab-runner-helper/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/gitlab-runner-helper/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/gitlab-runner-helper/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/gitlab-runner-helper/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/gitlab-runner-helper/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/gitlab-runner-helper/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/gitlab-runner-helper/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/gitlab-runner-helper/.github/workflows/stale.yml b/bitnami/gitlab-runner-helper/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/gitlab-runner-helper/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/gitlab-runner-helper/CODE_OF_CONDUCT.md b/bitnami/gitlab-runner-helper/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/gitlab-runner-helper/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/gitlab-runner-helper/CONTRIBUTING.md b/bitnami/gitlab-runner-helper/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/gitlab-runner-helper/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/gitlab-runner-helper/LICENSE.md b/bitnami/gitlab-runner-helper/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/gitlab-runner-helper/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/gitlab-runner/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/gitlab-runner/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/gitlab-runner/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/gitlab-runner/.github/ISSUE_TEMPLATE/config.yml b/bitnami/gitlab-runner/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/gitlab-runner/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/gitlab-runner/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/gitlab-runner/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/gitlab-runner/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/gitlab-runner/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/gitlab-runner/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/gitlab-runner/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/gitlab-runner/.github/workflows/stale.yml b/bitnami/gitlab-runner/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/gitlab-runner/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/gitlab-runner/CODE_OF_CONDUCT.md b/bitnami/gitlab-runner/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/gitlab-runner/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/gitlab-runner/CONTRIBUTING.md b/bitnami/gitlab-runner/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/gitlab-runner/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/gitlab-runner/LICENSE.md b/bitnami/gitlab-runner/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/gitlab-runner/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/golang/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/golang/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/golang/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/golang/.github/ISSUE_TEMPLATE/config.yml b/bitnami/golang/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/golang/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/golang/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/golang/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/golang/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/golang/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/golang/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/golang/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/golang/.github/workflows/stale.yml b/bitnami/golang/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/golang/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/golang/CODE_OF_CONDUCT.md b/bitnami/golang/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/golang/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/golang/CONTRIBUTING.md b/bitnami/golang/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/golang/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/golang/LICENSE.md b/bitnami/golang/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/golang/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/google-cloud-sdk/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/google-cloud-sdk/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/google-cloud-sdk/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/google-cloud-sdk/.github/ISSUE_TEMPLATE/config.yml b/bitnami/google-cloud-sdk/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/google-cloud-sdk/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/google-cloud-sdk/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/google-cloud-sdk/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/google-cloud-sdk/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/google-cloud-sdk/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/google-cloud-sdk/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/google-cloud-sdk/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/google-cloud-sdk/.github/workflows/stale.yml b/bitnami/google-cloud-sdk/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/google-cloud-sdk/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/google-cloud-sdk/CODE_OF_CONDUCT.md b/bitnami/google-cloud-sdk/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/google-cloud-sdk/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/google-cloud-sdk/CONTRIBUTING.md b/bitnami/google-cloud-sdk/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/google-cloud-sdk/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/google-cloud-sdk/LICENSE.md b/bitnami/google-cloud-sdk/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/google-cloud-sdk/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/gradle/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/gradle/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/gradle/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/gradle/.github/ISSUE_TEMPLATE/config.yml b/bitnami/gradle/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/gradle/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/gradle/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/gradle/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/gradle/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/gradle/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/gradle/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/gradle/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/gradle/.github/workflows/stale.yml b/bitnami/gradle/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/gradle/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/gradle/CODE_OF_CONDUCT.md b/bitnami/gradle/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/gradle/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/gradle/CONTRIBUTING.md b/bitnami/gradle/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/gradle/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/gradle/LICENSE.md b/bitnami/gradle/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/gradle/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/grafana-image-renderer/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/grafana-image-renderer/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/grafana-image-renderer/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/grafana-image-renderer/.github/ISSUE_TEMPLATE/config.yml b/bitnami/grafana-image-renderer/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/grafana-image-renderer/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/grafana-image-renderer/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/grafana-image-renderer/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/grafana-image-renderer/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/grafana-image-renderer/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/grafana-image-renderer/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/grafana-image-renderer/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/grafana-image-renderer/.github/workflows/stale.yml b/bitnami/grafana-image-renderer/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/grafana-image-renderer/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/grafana-image-renderer/CODE_OF_CONDUCT.md b/bitnami/grafana-image-renderer/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/grafana-image-renderer/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/grafana-image-renderer/CONTRIBUTING.md b/bitnami/grafana-image-renderer/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/grafana-image-renderer/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/grafana-image-renderer/LICENSE.md b/bitnami/grafana-image-renderer/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/grafana-image-renderer/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/grafana-operator/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/grafana-operator/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/grafana-operator/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/grafana-operator/.github/ISSUE_TEMPLATE/config.yml b/bitnami/grafana-operator/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/grafana-operator/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/grafana-operator/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/grafana-operator/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/grafana-operator/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/grafana-operator/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/grafana-operator/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/grafana-operator/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/grafana-operator/.github/workflows/stale.yml b/bitnami/grafana-operator/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/grafana-operator/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/grafana-operator/CODE_OF_CONDUCT.md b/bitnami/grafana-operator/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/grafana-operator/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/grafana-operator/CONTRIBUTING.md b/bitnami/grafana-operator/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/grafana-operator/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/grafana-operator/LICENSE.md b/bitnami/grafana-operator/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/grafana-operator/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/grafana-tempo-query/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/grafana-tempo-query/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/grafana-tempo-query/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/grafana-tempo-query/.github/ISSUE_TEMPLATE/config.yml b/bitnami/grafana-tempo-query/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/grafana-tempo-query/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/grafana-tempo-query/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/grafana-tempo-query/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/grafana-tempo-query/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/grafana-tempo-query/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/grafana-tempo-query/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/grafana-tempo-query/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/grafana-tempo-query/.github/workflows/stale.yml b/bitnami/grafana-tempo-query/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/grafana-tempo-query/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/grafana-tempo-query/CODE_OF_CONDUCT.md b/bitnami/grafana-tempo-query/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/grafana-tempo-query/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/grafana-tempo-query/CONTRIBUTING.md b/bitnami/grafana-tempo-query/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/grafana-tempo-query/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/grafana-tempo-query/LICENSE.md b/bitnami/grafana-tempo-query/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/grafana-tempo-query/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/grafana-tempo-vulture/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/grafana-tempo-vulture/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/grafana-tempo-vulture/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/grafana-tempo-vulture/.github/ISSUE_TEMPLATE/config.yml b/bitnami/grafana-tempo-vulture/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/grafana-tempo-vulture/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/grafana-tempo-vulture/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/grafana-tempo-vulture/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/grafana-tempo-vulture/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/grafana-tempo-vulture/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/grafana-tempo-vulture/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/grafana-tempo-vulture/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/grafana-tempo-vulture/.github/workflows/stale.yml b/bitnami/grafana-tempo-vulture/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/grafana-tempo-vulture/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/grafana-tempo-vulture/CODE_OF_CONDUCT.md b/bitnami/grafana-tempo-vulture/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/grafana-tempo-vulture/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/grafana-tempo-vulture/CONTRIBUTING.md b/bitnami/grafana-tempo-vulture/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/grafana-tempo-vulture/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/grafana-tempo-vulture/LICENSE.md b/bitnami/grafana-tempo-vulture/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/grafana-tempo-vulture/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/grafana-tempo/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/grafana-tempo/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/grafana-tempo/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/grafana-tempo/.github/ISSUE_TEMPLATE/config.yml b/bitnami/grafana-tempo/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/grafana-tempo/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/grafana-tempo/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/grafana-tempo/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/grafana-tempo/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/grafana-tempo/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/grafana-tempo/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/grafana-tempo/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/grafana-tempo/.github/workflows/stale.yml b/bitnami/grafana-tempo/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/grafana-tempo/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/grafana-tempo/CODE_OF_CONDUCT.md b/bitnami/grafana-tempo/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/grafana-tempo/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/grafana-tempo/CONTRIBUTING.md b/bitnami/grafana-tempo/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/grafana-tempo/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/grafana-tempo/LICENSE.md b/bitnami/grafana-tempo/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/grafana-tempo/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/grafana/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/grafana/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/grafana/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/grafana/.github/ISSUE_TEMPLATE/config.yml b/bitnami/grafana/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/grafana/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/grafana/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/grafana/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/grafana/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/grafana/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/grafana/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/grafana/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/grafana/.github/workflows/stale.yml b/bitnami/grafana/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/grafana/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/grafana/CODE_OF_CONDUCT.md b/bitnami/grafana/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/grafana/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/grafana/CONTRIBUTING.md b/bitnami/grafana/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/grafana/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/grafana/LICENSE.md b/bitnami/grafana/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/grafana/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/haproxy/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/haproxy/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/haproxy/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/haproxy/.github/ISSUE_TEMPLATE/config.yml b/bitnami/haproxy/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/haproxy/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/haproxy/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/haproxy/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/haproxy/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/haproxy/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/haproxy/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/haproxy/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/haproxy/.github/workflows/stale.yml b/bitnami/haproxy/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/haproxy/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/haproxy/CODE_OF_CONDUCT.md b/bitnami/haproxy/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/haproxy/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/haproxy/CONTRIBUTING.md b/bitnami/haproxy/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/haproxy/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/haproxy/LICENSE.md b/bitnami/haproxy/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/haproxy/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/harbor-adapter-clair/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/harbor-adapter-clair/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/harbor-adapter-clair/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/harbor-adapter-clair/.github/ISSUE_TEMPLATE/config.yml b/bitnami/harbor-adapter-clair/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/harbor-adapter-clair/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/harbor-adapter-clair/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/harbor-adapter-clair/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/harbor-adapter-clair/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/harbor-adapter-clair/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/harbor-adapter-clair/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/harbor-adapter-clair/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/harbor-adapter-clair/.github/workflows/stale.yml b/bitnami/harbor-adapter-clair/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/harbor-adapter-clair/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/harbor-adapter-clair/CODE_OF_CONDUCT.md b/bitnami/harbor-adapter-clair/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/harbor-adapter-clair/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/harbor-adapter-clair/CONTRIBUTING.md b/bitnami/harbor-adapter-clair/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/harbor-adapter-clair/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/harbor-adapter-clair/LICENSE.md b/bitnami/harbor-adapter-clair/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/harbor-adapter-clair/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/harbor-adapter-trivy/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/harbor-adapter-trivy/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/harbor-adapter-trivy/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/harbor-adapter-trivy/.github/ISSUE_TEMPLATE/config.yml b/bitnami/harbor-adapter-trivy/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/harbor-adapter-trivy/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/harbor-adapter-trivy/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/harbor-adapter-trivy/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/harbor-adapter-trivy/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/harbor-adapter-trivy/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/harbor-adapter-trivy/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/harbor-adapter-trivy/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/harbor-adapter-trivy/.github/workflows/stale.yml b/bitnami/harbor-adapter-trivy/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/harbor-adapter-trivy/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/harbor-adapter-trivy/CODE_OF_CONDUCT.md b/bitnami/harbor-adapter-trivy/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/harbor-adapter-trivy/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/harbor-adapter-trivy/CONTRIBUTING.md b/bitnami/harbor-adapter-trivy/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/harbor-adapter-trivy/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/harbor-adapter-trivy/LICENSE.md b/bitnami/harbor-adapter-trivy/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/harbor-adapter-trivy/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/harbor-clair/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/harbor-clair/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/harbor-clair/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/harbor-clair/.github/ISSUE_TEMPLATE/config.yml b/bitnami/harbor-clair/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/harbor-clair/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/harbor-clair/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/harbor-clair/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/harbor-clair/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/harbor-clair/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/harbor-clair/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/harbor-clair/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/harbor-clair/.github/workflows/stale.yml b/bitnami/harbor-clair/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/harbor-clair/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/harbor-clair/CODE_OF_CONDUCT.md b/bitnami/harbor-clair/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/harbor-clair/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/harbor-clair/CONTRIBUTING.md b/bitnami/harbor-clair/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/harbor-clair/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/harbor-clair/LICENSE.md b/bitnami/harbor-clair/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/harbor-clair/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/harbor-core/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/harbor-core/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/harbor-core/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/harbor-core/.github/ISSUE_TEMPLATE/config.yml b/bitnami/harbor-core/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/harbor-core/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/harbor-core/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/harbor-core/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/harbor-core/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/harbor-core/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/harbor-core/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/harbor-core/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/harbor-core/.github/workflows/stale.yml b/bitnami/harbor-core/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/harbor-core/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/harbor-core/CODE_OF_CONDUCT.md b/bitnami/harbor-core/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/harbor-core/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/harbor-core/CONTRIBUTING.md b/bitnami/harbor-core/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/harbor-core/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/harbor-core/LICENSE.md b/bitnami/harbor-core/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/harbor-core/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/harbor-exporter/.github/ISSUE_TEMPLATE.md b/bitnami/harbor-exporter/.github/ISSUE_TEMPLATE.md deleted file mode 100644 index a7a1a6fc7a0f..000000000000 --- a/bitnami/harbor-exporter/.github/ISSUE_TEMPLATE.md +++ /dev/null @@ -1,21 +0,0 @@ -**Description** - - - -**Steps to reproduce the issue:** - -1. [First Step] -2. [Second Step] -3. [and so on...] - -**Describe the results you received:** - - - -**Describe the results you expected:** - - - -**Additional information you deem important (e.g. issue happens only occasionally, environment details, etc.):** - - diff --git a/bitnami/harbor-exporter/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/harbor-exporter/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/harbor-exporter/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/harbor-exporter/.github/workflows/stale.yml b/bitnami/harbor-exporter/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/harbor-exporter/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/harbor-exporter/CODE_OF_CONDUCT.md b/bitnami/harbor-exporter/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/harbor-exporter/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/harbor-exporter/CONTRIBUTING.md b/bitnami/harbor-exporter/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/harbor-exporter/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/harbor-exporter/LICENSE.md b/bitnami/harbor-exporter/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/harbor-exporter/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/harbor-jobservice/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/harbor-jobservice/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/harbor-jobservice/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/harbor-jobservice/.github/ISSUE_TEMPLATE/config.yml b/bitnami/harbor-jobservice/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/harbor-jobservice/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/harbor-jobservice/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/harbor-jobservice/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/harbor-jobservice/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/harbor-jobservice/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/harbor-jobservice/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/harbor-jobservice/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/harbor-jobservice/.github/workflows/stale.yml b/bitnami/harbor-jobservice/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/harbor-jobservice/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/harbor-jobservice/CODE_OF_CONDUCT.md b/bitnami/harbor-jobservice/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/harbor-jobservice/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/harbor-jobservice/CONTRIBUTING.md b/bitnami/harbor-jobservice/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/harbor-jobservice/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/harbor-jobservice/LICENSE.md b/bitnami/harbor-jobservice/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/harbor-jobservice/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/harbor-notary-server/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/harbor-notary-server/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/harbor-notary-server/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/harbor-notary-server/.github/ISSUE_TEMPLATE/config.yml b/bitnami/harbor-notary-server/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/harbor-notary-server/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/harbor-notary-server/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/harbor-notary-server/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/harbor-notary-server/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/harbor-notary-server/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/harbor-notary-server/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/harbor-notary-server/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/harbor-notary-server/.github/workflows/stale.yml b/bitnami/harbor-notary-server/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/harbor-notary-server/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/harbor-notary-server/CODE_OF_CONDUCT.md b/bitnami/harbor-notary-server/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/harbor-notary-server/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/harbor-notary-server/CONTRIBUTING.md b/bitnami/harbor-notary-server/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/harbor-notary-server/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/harbor-notary-server/LICENSE.md b/bitnami/harbor-notary-server/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/harbor-notary-server/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/harbor-notary-signer/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/harbor-notary-signer/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/harbor-notary-signer/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/harbor-notary-signer/.github/ISSUE_TEMPLATE/config.yml b/bitnami/harbor-notary-signer/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/harbor-notary-signer/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/harbor-notary-signer/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/harbor-notary-signer/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/harbor-notary-signer/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/harbor-notary-signer/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/harbor-notary-signer/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/harbor-notary-signer/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/harbor-notary-signer/.github/workflows/stale.yml b/bitnami/harbor-notary-signer/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/harbor-notary-signer/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/harbor-notary-signer/CODE_OF_CONDUCT.md b/bitnami/harbor-notary-signer/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/harbor-notary-signer/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/harbor-notary-signer/CONTRIBUTING.md b/bitnami/harbor-notary-signer/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/harbor-notary-signer/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/harbor-notary-signer/LICENSE.md b/bitnami/harbor-notary-signer/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/harbor-notary-signer/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/harbor-portal/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/harbor-portal/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/harbor-portal/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/harbor-portal/.github/ISSUE_TEMPLATE/config.yml b/bitnami/harbor-portal/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/harbor-portal/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/harbor-portal/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/harbor-portal/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/harbor-portal/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/harbor-portal/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/harbor-portal/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/harbor-portal/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/harbor-portal/.github/workflows/stale.yml b/bitnami/harbor-portal/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/harbor-portal/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/harbor-portal/CODE_OF_CONDUCT.md b/bitnami/harbor-portal/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/harbor-portal/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/harbor-portal/CONTRIBUTING.md b/bitnami/harbor-portal/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/harbor-portal/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/harbor-portal/LICENSE.md b/bitnami/harbor-portal/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/harbor-portal/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/harbor-registry/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/harbor-registry/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/harbor-registry/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/harbor-registry/.github/ISSUE_TEMPLATE/config.yml b/bitnami/harbor-registry/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/harbor-registry/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/harbor-registry/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/harbor-registry/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/harbor-registry/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/harbor-registry/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/harbor-registry/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/harbor-registry/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/harbor-registry/.github/workflows/stale.yml b/bitnami/harbor-registry/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/harbor-registry/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/harbor-registry/CODE_OF_CONDUCT.md b/bitnami/harbor-registry/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/harbor-registry/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/harbor-registry/CONTRIBUTING.md b/bitnami/harbor-registry/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/harbor-registry/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/harbor-registry/LICENSE.md b/bitnami/harbor-registry/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/harbor-registry/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/harbor-registryctl/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/harbor-registryctl/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/harbor-registryctl/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/harbor-registryctl/.github/ISSUE_TEMPLATE/config.yml b/bitnami/harbor-registryctl/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/harbor-registryctl/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/harbor-registryctl/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/harbor-registryctl/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/harbor-registryctl/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/harbor-registryctl/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/harbor-registryctl/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/harbor-registryctl/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/harbor-registryctl/.github/workflows/stale.yml b/bitnami/harbor-registryctl/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/harbor-registryctl/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/harbor-registryctl/CODE_OF_CONDUCT.md b/bitnami/harbor-registryctl/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/harbor-registryctl/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/harbor-registryctl/CONTRIBUTING.md b/bitnami/harbor-registryctl/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/harbor-registryctl/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/harbor-registryctl/LICENSE.md b/bitnami/harbor-registryctl/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/harbor-registryctl/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/influxdb-relay/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/influxdb-relay/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/influxdb-relay/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/influxdb-relay/.github/ISSUE_TEMPLATE/config.yml b/bitnami/influxdb-relay/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/influxdb-relay/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/influxdb-relay/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/influxdb-relay/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/influxdb-relay/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/influxdb-relay/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/influxdb-relay/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/influxdb-relay/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/influxdb-relay/.github/workflows/stale.yml b/bitnami/influxdb-relay/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/influxdb-relay/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/influxdb-relay/CODE_OF_CONDUCT.md b/bitnami/influxdb-relay/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/influxdb-relay/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/influxdb-relay/CONTRIBUTING.md b/bitnami/influxdb-relay/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/influxdb-relay/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/influxdb-relay/LICENSE.md b/bitnami/influxdb-relay/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/influxdb-relay/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/influxdb/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/influxdb/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/influxdb/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/influxdb/.github/ISSUE_TEMPLATE/config.yml b/bitnami/influxdb/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/influxdb/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/influxdb/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/influxdb/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/influxdb/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/influxdb/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/influxdb/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/influxdb/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/influxdb/.github/workflows/stale.yml b/bitnami/influxdb/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/influxdb/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/influxdb/CODE_OF_CONDUCT.md b/bitnami/influxdb/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/influxdb/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/influxdb/CONTRIBUTING.md b/bitnami/influxdb/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/influxdb/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/influxdb/LICENSE.md b/bitnami/influxdb/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/influxdb/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/jasperreports/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/jasperreports/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/jasperreports/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/jasperreports/.github/ISSUE_TEMPLATE/config.yml b/bitnami/jasperreports/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/jasperreports/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/jasperreports/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/jasperreports/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/jasperreports/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/jasperreports/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/jasperreports/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/jasperreports/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/jasperreports/.github/workflows/stale.yml b/bitnami/jasperreports/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/jasperreports/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/jasperreports/CODE_OF_CONDUCT.md b/bitnami/jasperreports/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/jasperreports/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/jasperreports/CONTRIBUTING.md b/bitnami/jasperreports/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/jasperreports/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/jasperreports/LICENSE.md b/bitnami/jasperreports/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/jasperreports/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/java/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/java/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/java/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/java/.github/ISSUE_TEMPLATE/config.yml b/bitnami/java/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/java/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/java/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/java/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/java/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/java/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/java/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/java/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/java/.github/workflows/stale.yml b/bitnami/java/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/java/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/java/CODE_OF_CONDUCT.md b/bitnami/java/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/java/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/java/CONTRIBUTING.md b/bitnami/java/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/java/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/java/LICENSE.md b/bitnami/java/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/java/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/jenkins-exporter/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/jenkins-exporter/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/jenkins-exporter/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/jenkins-exporter/.github/ISSUE_TEMPLATE/config.yml b/bitnami/jenkins-exporter/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/jenkins-exporter/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/jenkins-exporter/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/jenkins-exporter/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/jenkins-exporter/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/jenkins-exporter/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/jenkins-exporter/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/jenkins-exporter/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/jenkins-exporter/.github/workflows/stale.yml b/bitnami/jenkins-exporter/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/jenkins-exporter/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/jenkins-exporter/CODE_OF_CONDUCT.md b/bitnami/jenkins-exporter/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/jenkins-exporter/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/jenkins-exporter/CONTRIBUTING.md b/bitnami/jenkins-exporter/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/jenkins-exporter/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/jenkins-exporter/LICENSE.md b/bitnami/jenkins-exporter/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/jenkins-exporter/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/jenkins/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/jenkins/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/jenkins/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/jenkins/.github/ISSUE_TEMPLATE/config.yml b/bitnami/jenkins/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/jenkins/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/jenkins/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/jenkins/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/jenkins/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/jenkins/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/jenkins/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/jenkins/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/jenkins/.github/workflows/stale.yml b/bitnami/jenkins/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/jenkins/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/jenkins/CODE_OF_CONDUCT.md b/bitnami/jenkins/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/jenkins/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/jenkins/CONTRIBUTING.md b/bitnami/jenkins/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/jenkins/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/jenkins/LICENSE.md b/bitnami/jenkins/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/jenkins/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/jmx-exporter/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/jmx-exporter/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/jmx-exporter/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/jmx-exporter/.github/ISSUE_TEMPLATE/config.yml b/bitnami/jmx-exporter/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/jmx-exporter/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/jmx-exporter/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/jmx-exporter/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/jmx-exporter/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/jmx-exporter/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/jmx-exporter/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/jmx-exporter/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/jmx-exporter/.github/workflows/stale.yml b/bitnami/jmx-exporter/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/jmx-exporter/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/jmx-exporter/CODE_OF_CONDUCT.md b/bitnami/jmx-exporter/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/jmx-exporter/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/jmx-exporter/CONTRIBUTING.md b/bitnami/jmx-exporter/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/jmx-exporter/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/jmx-exporter/LICENSE.md b/bitnami/jmx-exporter/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/jmx-exporter/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/joomla/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/joomla/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/joomla/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/joomla/.github/ISSUE_TEMPLATE/config.yml b/bitnami/joomla/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/joomla/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/joomla/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/joomla/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/joomla/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/joomla/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/joomla/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/joomla/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/joomla/.github/workflows/stale.yml b/bitnami/joomla/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/joomla/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/joomla/CODE_OF_CONDUCT.md b/bitnami/joomla/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/joomla/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/joomla/CONTRIBUTING.md b/bitnami/joomla/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/joomla/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/joomla/LICENSE.md b/bitnami/joomla/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/joomla/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/jruby/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/jruby/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/jruby/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/jruby/.github/ISSUE_TEMPLATE/config.yml b/bitnami/jruby/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/jruby/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/jruby/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/jruby/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/jruby/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/jruby/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/jruby/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/jruby/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/jruby/.github/workflows/stale.yml b/bitnami/jruby/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/jruby/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/jruby/CODE_OF_CONDUCT.md b/bitnami/jruby/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/jruby/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/jruby/CONTRIBUTING.md b/bitnami/jruby/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/jruby/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/jruby/LICENSE.md b/bitnami/jruby/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/jruby/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/jsonnet/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/jsonnet/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/jsonnet/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/jsonnet/.github/ISSUE_TEMPLATE/config.yml b/bitnami/jsonnet/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/jsonnet/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/jsonnet/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/jsonnet/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/jsonnet/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/jsonnet/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/jsonnet/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/jsonnet/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/jsonnet/.github/workflows/stale.yml b/bitnami/jsonnet/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/jsonnet/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/jsonnet/CODE_OF_CONDUCT.md b/bitnami/jsonnet/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/jsonnet/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/jsonnet/CONTRIBUTING.md b/bitnami/jsonnet/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/jsonnet/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/jsonnet/LICENSE.md b/bitnami/jsonnet/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/jsonnet/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/jupyter-base-notebook/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/jupyter-base-notebook/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/jupyter-base-notebook/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/jupyter-base-notebook/.github/ISSUE_TEMPLATE/config.yml b/bitnami/jupyter-base-notebook/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/jupyter-base-notebook/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/jupyter-base-notebook/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/jupyter-base-notebook/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/jupyter-base-notebook/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/jupyter-base-notebook/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/jupyter-base-notebook/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/jupyter-base-notebook/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/jupyter-base-notebook/.github/workflows/stale.yml b/bitnami/jupyter-base-notebook/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/jupyter-base-notebook/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/jupyter-base-notebook/CODE_OF_CONDUCT.md b/bitnami/jupyter-base-notebook/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/jupyter-base-notebook/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/jupyter-base-notebook/CONTRIBUTING.md b/bitnami/jupyter-base-notebook/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/jupyter-base-notebook/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/jupyter-base-notebook/LICENSE.md b/bitnami/jupyter-base-notebook/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/jupyter-base-notebook/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/jupyterhub/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/jupyterhub/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/jupyterhub/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/jupyterhub/.github/ISSUE_TEMPLATE/config.yml b/bitnami/jupyterhub/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/jupyterhub/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/jupyterhub/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/jupyterhub/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/jupyterhub/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/jupyterhub/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/jupyterhub/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/jupyterhub/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/jupyterhub/.github/workflows/stale.yml b/bitnami/jupyterhub/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/jupyterhub/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/jupyterhub/CODE_OF_CONDUCT.md b/bitnami/jupyterhub/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/jupyterhub/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/jupyterhub/CONTRIBUTING.md b/bitnami/jupyterhub/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/jupyterhub/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/jupyterhub/LICENSE.md b/bitnami/jupyterhub/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/jupyterhub/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/kafka-exporter/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/kafka-exporter/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/kafka-exporter/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/kafka-exporter/.github/ISSUE_TEMPLATE/config.yml b/bitnami/kafka-exporter/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/kafka-exporter/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/kafka-exporter/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/kafka-exporter/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/kafka-exporter/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/kafka-exporter/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/kafka-exporter/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/kafka-exporter/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/kafka-exporter/.github/workflows/stale.yml b/bitnami/kafka-exporter/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/kafka-exporter/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/kafka-exporter/CODE_OF_CONDUCT.md b/bitnami/kafka-exporter/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/kafka-exporter/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/kafka-exporter/CONTRIBUTING.md b/bitnami/kafka-exporter/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/kafka-exporter/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/kafka-exporter/LICENSE.md b/bitnami/kafka-exporter/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/kafka-exporter/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/kafka/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/kafka/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/kafka/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/kafka/.github/ISSUE_TEMPLATE/config.yml b/bitnami/kafka/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/kafka/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/kafka/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/kafka/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/kafka/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/kafka/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/kafka/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/kafka/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/kafka/.github/workflows/stale.yml b/bitnami/kafka/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/kafka/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/kafka/CODE_OF_CONDUCT.md b/bitnami/kafka/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/kafka/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/kafka/CONTRIBUTING.md b/bitnami/kafka/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/kafka/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/kafka/LICENSE.md b/bitnami/kafka/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/kafka/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/kapacitor/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/kapacitor/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/kapacitor/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/kapacitor/.github/ISSUE_TEMPLATE/config.yml b/bitnami/kapacitor/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/kapacitor/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/kapacitor/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/kapacitor/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/kapacitor/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/kapacitor/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/kapacitor/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/kapacitor/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/kapacitor/.github/workflows/stale.yml b/bitnami/kapacitor/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/kapacitor/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/kapacitor/CODE_OF_CONDUCT.md b/bitnami/kapacitor/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/kapacitor/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/kapacitor/CONTRIBUTING.md b/bitnami/kapacitor/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/kapacitor/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/kapacitor/LICENSE.md b/bitnami/kapacitor/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/kapacitor/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/keycloak-config-cli/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/keycloak-config-cli/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/keycloak-config-cli/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/keycloak-config-cli/.github/ISSUE_TEMPLATE/config.yml b/bitnami/keycloak-config-cli/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/keycloak-config-cli/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/keycloak-config-cli/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/keycloak-config-cli/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/keycloak-config-cli/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/keycloak-config-cli/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/keycloak-config-cli/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/keycloak-config-cli/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/keycloak-config-cli/.github/workflows/stale.yml b/bitnami/keycloak-config-cli/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/keycloak-config-cli/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/keycloak-config-cli/CODE_OF_CONDUCT.md b/bitnami/keycloak-config-cli/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/keycloak-config-cli/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/keycloak-config-cli/CONTRIBUTING.md b/bitnami/keycloak-config-cli/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/keycloak-config-cli/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/keycloak-config-cli/LICENSE.md b/bitnami/keycloak-config-cli/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/keycloak-config-cli/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/keycloak-gatekeeper/.github/ISSUE_TEMPLATE.md b/bitnami/keycloak-gatekeeper/.github/ISSUE_TEMPLATE.md deleted file mode 100644 index 91afdfd82d31..000000000000 --- a/bitnami/keycloak-gatekeeper/.github/ISSUE_TEMPLATE.md +++ /dev/null @@ -1,22 +0,0 @@ -**Description** - - - -**Steps to reproduce the issue:** - -1. [First Step] -2. [Second Step] -3. [and so on...] - -**Describe the results you received:** - - - -**Describe the results you expected:** - - - -**Additional information you deem important (e.g. issue happens only occasionally, environment details, etc.):** - - - diff --git a/bitnami/keycloak-gatekeeper/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/keycloak-gatekeeper/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/keycloak-gatekeeper/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/keycloak-gatekeeper/.github/workflows/stale.yml b/bitnami/keycloak-gatekeeper/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/keycloak-gatekeeper/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/keycloak-gatekeeper/CODE_OF_CONDUCT.md b/bitnami/keycloak-gatekeeper/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/keycloak-gatekeeper/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/keycloak-gatekeeper/CONTRIBUTING.md b/bitnami/keycloak-gatekeeper/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/keycloak-gatekeeper/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/keycloak-gatekeeper/LICENSE.md b/bitnami/keycloak-gatekeeper/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/keycloak-gatekeeper/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/keycloak/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/keycloak/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/keycloak/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/keycloak/.github/ISSUE_TEMPLATE/config.yml b/bitnami/keycloak/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/keycloak/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/keycloak/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/keycloak/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/keycloak/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/keycloak/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/keycloak/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/keycloak/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/keycloak/.github/workflows/stale.yml b/bitnami/keycloak/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/keycloak/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/keycloak/CODE_OF_CONDUCT.md b/bitnami/keycloak/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/keycloak/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/keycloak/CONTRIBUTING.md b/bitnami/keycloak/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/keycloak/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/keycloak/LICENSE.md b/bitnami/keycloak/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/keycloak/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/kiam/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/kiam/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/kiam/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/kiam/.github/ISSUE_TEMPLATE/config.yml b/bitnami/kiam/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/kiam/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/kiam/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/kiam/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/kiam/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/kiam/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/kiam/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/kiam/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/kiam/.github/workflows/stale.yml b/bitnami/kiam/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/kiam/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/kiam/CODE_OF_CONDUCT.md b/bitnami/kiam/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/kiam/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/kiam/CONTRIBUTING.md b/bitnami/kiam/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/kiam/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/kiam/LICENSE.md b/bitnami/kiam/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/kiam/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/kibana/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/kibana/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/kibana/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/kibana/.github/ISSUE_TEMPLATE/config.yml b/bitnami/kibana/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/kibana/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/kibana/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/kibana/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/kibana/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/kibana/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/kibana/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/kibana/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/kibana/.github/workflows/stale.yml b/bitnami/kibana/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/kibana/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/kibana/CODE_OF_CONDUCT.md b/bitnami/kibana/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/kibana/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/kibana/CONTRIBUTING.md b/bitnami/kibana/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/kibana/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/kibana/LICENSE.md b/bitnami/kibana/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/kibana/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/kong-ingress-controller/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/kong-ingress-controller/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/kong-ingress-controller/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/kong-ingress-controller/.github/ISSUE_TEMPLATE/config.yml b/bitnami/kong-ingress-controller/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/kong-ingress-controller/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/kong-ingress-controller/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/kong-ingress-controller/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/kong-ingress-controller/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/kong-ingress-controller/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/kong-ingress-controller/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/kong-ingress-controller/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/kong-ingress-controller/.github/workflows/stale.yml b/bitnami/kong-ingress-controller/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/kong-ingress-controller/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/kong-ingress-controller/CODE_OF_CONDUCT.md b/bitnami/kong-ingress-controller/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/kong-ingress-controller/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/kong-ingress-controller/CONTRIBUTING.md b/bitnami/kong-ingress-controller/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/kong-ingress-controller/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/kong-ingress-controller/LICENSE.md b/bitnami/kong-ingress-controller/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/kong-ingress-controller/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/kong/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/kong/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/kong/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/kong/.github/ISSUE_TEMPLATE/config.yml b/bitnami/kong/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/kong/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/kong/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/kong/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/kong/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/kong/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/kong/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/kong/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/kong/.github/workflows/stale.yml b/bitnami/kong/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/kong/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/kong/CODE_OF_CONDUCT.md b/bitnami/kong/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/kong/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/kong/CONTRIBUTING.md b/bitnami/kong/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/kong/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/kong/LICENSE.md b/bitnami/kong/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/kong/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/kube-rbac-proxy/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/kube-rbac-proxy/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/kube-rbac-proxy/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/kube-rbac-proxy/.github/ISSUE_TEMPLATE/config.yml b/bitnami/kube-rbac-proxy/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/kube-rbac-proxy/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/kube-rbac-proxy/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/kube-rbac-proxy/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/kube-rbac-proxy/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/kube-rbac-proxy/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/kube-rbac-proxy/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/kube-rbac-proxy/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/kube-rbac-proxy/.github/workflows/stale.yml b/bitnami/kube-rbac-proxy/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/kube-rbac-proxy/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/kube-rbac-proxy/CODE_OF_CONDUCT.md b/bitnami/kube-rbac-proxy/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/kube-rbac-proxy/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/kube-rbac-proxy/CONTRIBUTING.md b/bitnami/kube-rbac-proxy/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/kube-rbac-proxy/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/kube-rbac-proxy/LICENSE.md b/bitnami/kube-rbac-proxy/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/kube-rbac-proxy/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/kube-state-metrics/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/kube-state-metrics/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/kube-state-metrics/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/kube-state-metrics/.github/ISSUE_TEMPLATE/config.yml b/bitnami/kube-state-metrics/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/kube-state-metrics/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/kube-state-metrics/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/kube-state-metrics/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/kube-state-metrics/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/kube-state-metrics/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/kube-state-metrics/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/kube-state-metrics/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/kube-state-metrics/.github/workflows/stale.yml b/bitnami/kube-state-metrics/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/kube-state-metrics/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/kube-state-metrics/CODE_OF_CONDUCT.md b/bitnami/kube-state-metrics/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/kube-state-metrics/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/kube-state-metrics/CONTRIBUTING.md b/bitnami/kube-state-metrics/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/kube-state-metrics/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/kube-state-metrics/LICENSE.md b/bitnami/kube-state-metrics/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/kube-state-metrics/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/kubeapps-apis/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/kubeapps-apis/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/kubeapps-apis/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/kubeapps-apis/.github/ISSUE_TEMPLATE/config.yml b/bitnami/kubeapps-apis/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/kubeapps-apis/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/kubeapps-apis/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/kubeapps-apis/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/kubeapps-apis/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/kubeapps-apis/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/kubeapps-apis/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/kubeapps-apis/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/kubeapps-apis/.github/workflows/stale.yml b/bitnami/kubeapps-apis/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/kubeapps-apis/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/kubeapps-apis/CODE_OF_CONDUCT.md b/bitnami/kubeapps-apis/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/kubeapps-apis/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/kubeapps-apis/CONTRIBUTING.md b/bitnami/kubeapps-apis/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/kubeapps-apis/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/kubeapps-apis/LICENSE.md b/bitnami/kubeapps-apis/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/kubeapps-apis/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/kubeapps-apprepository-controller/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/kubeapps-apprepository-controller/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/kubeapps-apprepository-controller/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/kubeapps-apprepository-controller/.github/ISSUE_TEMPLATE/config.yml b/bitnami/kubeapps-apprepository-controller/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/kubeapps-apprepository-controller/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/kubeapps-apprepository-controller/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/kubeapps-apprepository-controller/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/kubeapps-apprepository-controller/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/kubeapps-apprepository-controller/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/kubeapps-apprepository-controller/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/kubeapps-apprepository-controller/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/kubeapps-apprepository-controller/.github/workflows/stale.yml b/bitnami/kubeapps-apprepository-controller/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/kubeapps-apprepository-controller/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/kubeapps-apprepository-controller/CODE_OF_CONDUCT.md b/bitnami/kubeapps-apprepository-controller/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/kubeapps-apprepository-controller/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/kubeapps-apprepository-controller/CONTRIBUTING.md b/bitnami/kubeapps-apprepository-controller/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/kubeapps-apprepository-controller/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/kubeapps-apprepository-controller/LICENSE.md b/bitnami/kubeapps-apprepository-controller/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/kubeapps-apprepository-controller/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/kubeapps-asset-syncer/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/kubeapps-asset-syncer/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/kubeapps-asset-syncer/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/kubeapps-asset-syncer/.github/ISSUE_TEMPLATE/config.yml b/bitnami/kubeapps-asset-syncer/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/kubeapps-asset-syncer/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/kubeapps-asset-syncer/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/kubeapps-asset-syncer/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/kubeapps-asset-syncer/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/kubeapps-asset-syncer/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/kubeapps-asset-syncer/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/kubeapps-asset-syncer/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/kubeapps-asset-syncer/.github/workflows/stale.yml b/bitnami/kubeapps-asset-syncer/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/kubeapps-asset-syncer/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/kubeapps-asset-syncer/CODE_OF_CONDUCT.md b/bitnami/kubeapps-asset-syncer/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/kubeapps-asset-syncer/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/kubeapps-asset-syncer/CONTRIBUTING.md b/bitnami/kubeapps-asset-syncer/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/kubeapps-asset-syncer/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/kubeapps-asset-syncer/LICENSE.md b/bitnami/kubeapps-asset-syncer/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/kubeapps-asset-syncer/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/kubeapps-assetsvc/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/kubeapps-assetsvc/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/kubeapps-assetsvc/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/kubeapps-assetsvc/.github/ISSUE_TEMPLATE/config.yml b/bitnami/kubeapps-assetsvc/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/kubeapps-assetsvc/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/kubeapps-assetsvc/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/kubeapps-assetsvc/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/kubeapps-assetsvc/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/kubeapps-assetsvc/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/kubeapps-assetsvc/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/kubeapps-assetsvc/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/kubeapps-assetsvc/.github/workflows/stale.yml b/bitnami/kubeapps-assetsvc/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/kubeapps-assetsvc/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/kubeapps-assetsvc/CODE_OF_CONDUCT.md b/bitnami/kubeapps-assetsvc/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/kubeapps-assetsvc/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/kubeapps-assetsvc/CONTRIBUTING.md b/bitnami/kubeapps-assetsvc/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/kubeapps-assetsvc/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/kubeapps-assetsvc/LICENSE.md b/bitnami/kubeapps-assetsvc/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/kubeapps-assetsvc/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/kubeapps-dashboard/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/kubeapps-dashboard/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/kubeapps-dashboard/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/kubeapps-dashboard/.github/ISSUE_TEMPLATE/config.yml b/bitnami/kubeapps-dashboard/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/kubeapps-dashboard/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/kubeapps-dashboard/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/kubeapps-dashboard/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/kubeapps-dashboard/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/kubeapps-dashboard/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/kubeapps-dashboard/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/kubeapps-dashboard/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/kubeapps-dashboard/.github/workflows/stale.yml b/bitnami/kubeapps-dashboard/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/kubeapps-dashboard/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/kubeapps-dashboard/CODE_OF_CONDUCT.md b/bitnami/kubeapps-dashboard/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/kubeapps-dashboard/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/kubeapps-dashboard/CONTRIBUTING.md b/bitnami/kubeapps-dashboard/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/kubeapps-dashboard/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/kubeapps-dashboard/LICENSE.md b/bitnami/kubeapps-dashboard/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/kubeapps-dashboard/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/kubeapps-kubeops/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/kubeapps-kubeops/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/kubeapps-kubeops/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/kubeapps-kubeops/.github/ISSUE_TEMPLATE/config.yml b/bitnami/kubeapps-kubeops/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/kubeapps-kubeops/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/kubeapps-kubeops/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/kubeapps-kubeops/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/kubeapps-kubeops/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/kubeapps-kubeops/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/kubeapps-kubeops/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/kubeapps-kubeops/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/kubeapps-kubeops/.github/workflows/stale.yml b/bitnami/kubeapps-kubeops/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/kubeapps-kubeops/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/kubeapps-kubeops/CODE_OF_CONDUCT.md b/bitnami/kubeapps-kubeops/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/kubeapps-kubeops/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/kubeapps-kubeops/CONTRIBUTING.md b/bitnami/kubeapps-kubeops/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/kubeapps-kubeops/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/kubeapps-kubeops/LICENSE.md b/bitnami/kubeapps-kubeops/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/kubeapps-kubeops/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/kubeapps-pinniped-proxy/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/kubeapps-pinniped-proxy/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/kubeapps-pinniped-proxy/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/kubeapps-pinniped-proxy/.github/ISSUE_TEMPLATE/config.yml b/bitnami/kubeapps-pinniped-proxy/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/kubeapps-pinniped-proxy/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/kubeapps-pinniped-proxy/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/kubeapps-pinniped-proxy/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/kubeapps-pinniped-proxy/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/kubeapps-pinniped-proxy/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/kubeapps-pinniped-proxy/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/kubeapps-pinniped-proxy/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/kubeapps-pinniped-proxy/.github/workflows/stale.yml b/bitnami/kubeapps-pinniped-proxy/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/kubeapps-pinniped-proxy/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/kubeapps-pinniped-proxy/CODE_OF_CONDUCT.md b/bitnami/kubeapps-pinniped-proxy/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/kubeapps-pinniped-proxy/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/kubeapps-pinniped-proxy/CONTRIBUTING.md b/bitnami/kubeapps-pinniped-proxy/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/kubeapps-pinniped-proxy/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/kubeapps-pinniped-proxy/LICENSE.md b/bitnami/kubeapps-pinniped-proxy/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/kubeapps-pinniped-proxy/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/kubectl/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/kubectl/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/kubectl/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/kubectl/.github/ISSUE_TEMPLATE/config.yml b/bitnami/kubectl/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/kubectl/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/kubectl/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/kubectl/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/kubectl/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/kubectl/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/kubectl/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/kubectl/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/kubectl/.github/workflows/stale.yml b/bitnami/kubectl/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/kubectl/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/kubectl/CODE_OF_CONDUCT.md b/bitnami/kubectl/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/kubectl/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/kubectl/CONTRIBUTING.md b/bitnami/kubectl/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/kubectl/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/kubectl/LICENSE.md b/bitnami/kubectl/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/kubectl/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/kubernetes-event-exporter/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/kubernetes-event-exporter/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/kubernetes-event-exporter/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/kubernetes-event-exporter/.github/ISSUE_TEMPLATE/config.yml b/bitnami/kubernetes-event-exporter/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/kubernetes-event-exporter/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/kubernetes-event-exporter/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/kubernetes-event-exporter/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/kubernetes-event-exporter/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/kubernetes-event-exporter/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/kubernetes-event-exporter/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/kubernetes-event-exporter/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/kubernetes-event-exporter/.github/workflows/stale.yml b/bitnami/kubernetes-event-exporter/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/kubernetes-event-exporter/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/kubernetes-event-exporter/CODE_OF_CONDUCT.md b/bitnami/kubernetes-event-exporter/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/kubernetes-event-exporter/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/kubernetes-event-exporter/CONTRIBUTING.md b/bitnami/kubernetes-event-exporter/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/kubernetes-event-exporter/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/kubernetes-event-exporter/LICENSE.md b/bitnami/kubernetes-event-exporter/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/kubernetes-event-exporter/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/kubewatch/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/kubewatch/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/kubewatch/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/kubewatch/.github/ISSUE_TEMPLATE/config.yml b/bitnami/kubewatch/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/kubewatch/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/kubewatch/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/kubewatch/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/kubewatch/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/kubewatch/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/kubewatch/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/kubewatch/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/kubewatch/.github/workflows/stale.yml b/bitnami/kubewatch/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/kubewatch/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/kubewatch/CODE_OF_CONDUCT.md b/bitnami/kubewatch/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/kubewatch/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/kubewatch/CONTRIBUTING.md b/bitnami/kubewatch/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/kubewatch/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/kubewatch/LICENSE.md b/bitnami/kubewatch/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/kubewatch/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/laravel/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/laravel/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/laravel/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/laravel/.github/ISSUE_TEMPLATE/config.yml b/bitnami/laravel/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/laravel/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/laravel/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/laravel/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/laravel/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/laravel/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/laravel/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/laravel/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/laravel/.github/workflows/stale.yml b/bitnami/laravel/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/laravel/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/laravel/CODE_OF_CONDUCT.md b/bitnami/laravel/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/laravel/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/laravel/CONTRIBUTING.md b/bitnami/laravel/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/laravel/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/laravel/LICENSE.md b/bitnami/laravel/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/laravel/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/logstash-exporter/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/logstash-exporter/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/logstash-exporter/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/logstash-exporter/.github/ISSUE_TEMPLATE/config.yml b/bitnami/logstash-exporter/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/logstash-exporter/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/logstash-exporter/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/logstash-exporter/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/logstash-exporter/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/logstash-exporter/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/logstash-exporter/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/logstash-exporter/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/logstash-exporter/.github/workflows/stale.yml b/bitnami/logstash-exporter/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/logstash-exporter/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/logstash-exporter/CODE_OF_CONDUCT.md b/bitnami/logstash-exporter/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/logstash-exporter/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/logstash-exporter/CONTRIBUTING.md b/bitnami/logstash-exporter/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/logstash-exporter/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/logstash-exporter/LICENSE.md b/bitnami/logstash-exporter/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/logstash-exporter/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/logstash/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/logstash/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/logstash/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/logstash/.github/ISSUE_TEMPLATE/config.yml b/bitnami/logstash/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/logstash/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/logstash/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/logstash/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/logstash/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/logstash/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/logstash/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/logstash/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/logstash/.github/workflows/stale.yml b/bitnami/logstash/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/logstash/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/logstash/CODE_OF_CONDUCT.md b/bitnami/logstash/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/logstash/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/logstash/CONTRIBUTING.md b/bitnami/logstash/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/logstash/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/logstash/LICENSE.md b/bitnami/logstash/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/logstash/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/magento/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/magento/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/magento/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/magento/.github/ISSUE_TEMPLATE/config.yml b/bitnami/magento/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/magento/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/magento/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/magento/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/magento/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/magento/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/magento/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/magento/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/magento/.github/workflows/stale.yml b/bitnami/magento/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/magento/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/magento/CODE_OF_CONDUCT.md b/bitnami/magento/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/magento/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/magento/CONTRIBUTING.md b/bitnami/magento/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/magento/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/magento/LICENSE.md b/bitnami/magento/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/magento/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/mariadb-galera/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/mariadb-galera/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/mariadb-galera/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/mariadb-galera/.github/ISSUE_TEMPLATE/config.yml b/bitnami/mariadb-galera/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/mariadb-galera/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/mariadb-galera/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/mariadb-galera/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/mariadb-galera/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/mariadb-galera/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/mariadb-galera/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/mariadb-galera/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/mariadb-galera/.github/workflows/stale.yml b/bitnami/mariadb-galera/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/mariadb-galera/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/mariadb-galera/CODE_OF_CONDUCT.md b/bitnami/mariadb-galera/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/mariadb-galera/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/mariadb-galera/CONTRIBUTING.md b/bitnami/mariadb-galera/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/mariadb-galera/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/mariadb-galera/LICENSE.md b/bitnami/mariadb-galera/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/mariadb-galera/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/mariadb/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/mariadb/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/mariadb/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/mariadb/.github/ISSUE_TEMPLATE/config.yml b/bitnami/mariadb/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/mariadb/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/mariadb/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/mariadb/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/mariadb/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/mariadb/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/mariadb/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/mariadb/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/mariadb/.github/workflows/stale.yml b/bitnami/mariadb/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/mariadb/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/mariadb/CODE_OF_CONDUCT.md b/bitnami/mariadb/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/mariadb/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/mariadb/CONTRIBUTING.md b/bitnami/mariadb/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/mariadb/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/mariadb/LICENSE.md b/bitnami/mariadb/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/mariadb/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/matomo/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/matomo/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/matomo/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/matomo/.github/ISSUE_TEMPLATE/config.yml b/bitnami/matomo/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/matomo/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/matomo/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/matomo/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/matomo/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/matomo/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/matomo/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/matomo/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/matomo/.github/workflows/stale.yml b/bitnami/matomo/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/matomo/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/matomo/CODE_OF_CONDUCT.md b/bitnami/matomo/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/matomo/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/matomo/CONTRIBUTING.md b/bitnami/matomo/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/matomo/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/matomo/LICENSE.md b/bitnami/matomo/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/matomo/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/mediawiki/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/mediawiki/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/mediawiki/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/mediawiki/.github/ISSUE_TEMPLATE/config.yml b/bitnami/mediawiki/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/mediawiki/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/mediawiki/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/mediawiki/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/mediawiki/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/mediawiki/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/mediawiki/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/mediawiki/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/mediawiki/.github/workflows/stale.yml b/bitnami/mediawiki/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/mediawiki/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/mediawiki/CODE_OF_CONDUCT.md b/bitnami/mediawiki/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/mediawiki/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/mediawiki/CONTRIBUTING.md b/bitnami/mediawiki/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/mediawiki/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/mediawiki/LICENSE.md b/bitnami/mediawiki/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/mediawiki/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/memcached-exporter/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/memcached-exporter/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/memcached-exporter/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/memcached-exporter/.github/ISSUE_TEMPLATE/config.yml b/bitnami/memcached-exporter/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/memcached-exporter/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/memcached-exporter/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/memcached-exporter/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/memcached-exporter/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/memcached-exporter/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/memcached-exporter/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/memcached-exporter/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/memcached-exporter/.github/workflows/stale.yml b/bitnami/memcached-exporter/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/memcached-exporter/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/memcached-exporter/CODE_OF_CONDUCT.md b/bitnami/memcached-exporter/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/memcached-exporter/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/memcached-exporter/CONTRIBUTING.md b/bitnami/memcached-exporter/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/memcached-exporter/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/memcached-exporter/LICENSE.md b/bitnami/memcached-exporter/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/memcached-exporter/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/memcached/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/memcached/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/memcached/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/memcached/.github/ISSUE_TEMPLATE/config.yml b/bitnami/memcached/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/memcached/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/memcached/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/memcached/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/memcached/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/memcached/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/memcached/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/memcached/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/memcached/.github/workflows/stale.yml b/bitnami/memcached/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/memcached/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/memcached/CODE_OF_CONDUCT.md b/bitnami/memcached/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/memcached/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/memcached/CONTRIBUTING.md b/bitnami/memcached/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/memcached/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/memcached/LICENSE.md b/bitnami/memcached/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/memcached/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/metallb-controller/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/metallb-controller/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/metallb-controller/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/metallb-controller/.github/ISSUE_TEMPLATE/config.yml b/bitnami/metallb-controller/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/metallb-controller/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/metallb-controller/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/metallb-controller/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/metallb-controller/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/metallb-controller/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/metallb-controller/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/metallb-controller/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/metallb-controller/.github/workflows/stale.yml b/bitnami/metallb-controller/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/metallb-controller/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/metallb-controller/CODE_OF_CONDUCT.md b/bitnami/metallb-controller/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/metallb-controller/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/metallb-controller/CONTRIBUTING.md b/bitnami/metallb-controller/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/metallb-controller/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/metallb-controller/LICENSE.md b/bitnami/metallb-controller/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/metallb-controller/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/metallb-speaker/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/metallb-speaker/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/metallb-speaker/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/metallb-speaker/.github/ISSUE_TEMPLATE/config.yml b/bitnami/metallb-speaker/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/metallb-speaker/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/metallb-speaker/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/metallb-speaker/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/metallb-speaker/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/metallb-speaker/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/metallb-speaker/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/metallb-speaker/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/metallb-speaker/.github/workflows/stale.yml b/bitnami/metallb-speaker/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/metallb-speaker/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/metallb-speaker/CODE_OF_CONDUCT.md b/bitnami/metallb-speaker/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/metallb-speaker/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/metallb-speaker/CONTRIBUTING.md b/bitnami/metallb-speaker/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/metallb-speaker/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/metallb-speaker/LICENSE.md b/bitnami/metallb-speaker/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/metallb-speaker/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/metrics-server/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/metrics-server/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/metrics-server/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/metrics-server/.github/ISSUE_TEMPLATE/config.yml b/bitnami/metrics-server/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/metrics-server/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/metrics-server/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/metrics-server/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/metrics-server/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/metrics-server/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/metrics-server/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/metrics-server/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/metrics-server/.github/workflows/stale.yml b/bitnami/metrics-server/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/metrics-server/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/metrics-server/CODE_OF_CONDUCT.md b/bitnami/metrics-server/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/metrics-server/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/metrics-server/CONTRIBUTING.md b/bitnami/metrics-server/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/metrics-server/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/metrics-server/LICENSE.md b/bitnami/metrics-server/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/metrics-server/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/minio-client/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/minio-client/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/minio-client/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/minio-client/.github/ISSUE_TEMPLATE/config.yml b/bitnami/minio-client/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/minio-client/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/minio-client/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/minio-client/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/minio-client/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/minio-client/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/minio-client/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/minio-client/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/minio-client/.github/workflows/stale.yml b/bitnami/minio-client/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/minio-client/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/minio-client/CODE_OF_CONDUCT.md b/bitnami/minio-client/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/minio-client/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/minio-client/CONTRIBUTING.md b/bitnami/minio-client/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/minio-client/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/minio-client/LICENSE.md b/bitnami/minio-client/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/minio-client/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/minio/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/minio/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/minio/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/minio/.github/ISSUE_TEMPLATE/config.yml b/bitnami/minio/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/minio/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/minio/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/minio/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/minio/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/minio/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/minio/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/minio/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/minio/.github/workflows/stale.yml b/bitnami/minio/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/minio/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/minio/CODE_OF_CONDUCT.md b/bitnami/minio/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/minio/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/minio/CONTRIBUTING.md b/bitnami/minio/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/minio/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/minio/LICENSE.md b/bitnami/minio/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/minio/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/mongodb-exporter/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/mongodb-exporter/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/mongodb-exporter/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/mongodb-exporter/.github/ISSUE_TEMPLATE/config.yml b/bitnami/mongodb-exporter/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/mongodb-exporter/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/mongodb-exporter/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/mongodb-exporter/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/mongodb-exporter/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/mongodb-exporter/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/mongodb-exporter/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/mongodb-exporter/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/mongodb-exporter/.github/workflows/stale.yml b/bitnami/mongodb-exporter/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/mongodb-exporter/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/mongodb-exporter/CODE_OF_CONDUCT.md b/bitnami/mongodb-exporter/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/mongodb-exporter/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/mongodb-exporter/CONTRIBUTING.md b/bitnami/mongodb-exporter/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/mongodb-exporter/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/mongodb-exporter/LICENSE.md b/bitnami/mongodb-exporter/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/mongodb-exporter/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/mongodb-sharded/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/mongodb-sharded/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/mongodb-sharded/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/mongodb-sharded/.github/ISSUE_TEMPLATE/config.yml b/bitnami/mongodb-sharded/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/mongodb-sharded/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/mongodb-sharded/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/mongodb-sharded/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/mongodb-sharded/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/mongodb-sharded/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/mongodb-sharded/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/mongodb-sharded/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/mongodb-sharded/.github/workflows/stale.yml b/bitnami/mongodb-sharded/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/mongodb-sharded/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/mongodb-sharded/CODE_OF_CONDUCT.md b/bitnami/mongodb-sharded/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/mongodb-sharded/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/mongodb-sharded/CONTRIBUTING.md b/bitnami/mongodb-sharded/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/mongodb-sharded/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/mongodb-sharded/LICENSE.md b/bitnami/mongodb-sharded/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/mongodb-sharded/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/mongodb/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/mongodb/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/mongodb/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/mongodb/.github/ISSUE_TEMPLATE/config.yml b/bitnami/mongodb/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/mongodb/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/mongodb/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/mongodb/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/mongodb/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/mongodb/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/mongodb/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/mongodb/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/mongodb/.github/workflows/stale.yml b/bitnami/mongodb/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/mongodb/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/mongodb/CODE_OF_CONDUCT.md b/bitnami/mongodb/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/mongodb/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/mongodb/CONTRIBUTING.md b/bitnami/mongodb/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/mongodb/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/mongodb/LICENSE.md b/bitnami/mongodb/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/mongodb/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/moodle/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/moodle/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/moodle/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/moodle/.github/ISSUE_TEMPLATE/config.yml b/bitnami/moodle/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/moodle/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/moodle/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/moodle/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/moodle/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/moodle/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/moodle/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/moodle/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/moodle/.github/workflows/stale.yml b/bitnami/moodle/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/moodle/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/moodle/CODE_OF_CONDUCT.md b/bitnami/moodle/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/moodle/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/moodle/CONTRIBUTING.md b/bitnami/moodle/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/moodle/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/moodle/LICENSE.md b/bitnami/moodle/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/moodle/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/mxnet/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/mxnet/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/mxnet/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/mxnet/.github/ISSUE_TEMPLATE/config.yml b/bitnami/mxnet/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/mxnet/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/mxnet/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/mxnet/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/mxnet/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/mxnet/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/mxnet/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/mxnet/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/mxnet/.github/workflows/stale.yml b/bitnami/mxnet/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/mxnet/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/mxnet/CODE_OF_CONDUCT.md b/bitnami/mxnet/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/mxnet/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/mxnet/CONTRIBUTING.md b/bitnami/mxnet/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/mxnet/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/mxnet/LICENSE.md b/bitnami/mxnet/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/mxnet/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/mysql/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/mysql/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/mysql/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/mysql/.github/ISSUE_TEMPLATE/config.yml b/bitnami/mysql/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/mysql/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/mysql/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/mysql/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/mysql/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/mysql/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/mysql/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/mysql/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/mysql/.github/workflows/stale.yml b/bitnami/mysql/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/mysql/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/mysql/CODE_OF_CONDUCT.md b/bitnami/mysql/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/mysql/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/mysql/CONTRIBUTING.md b/bitnami/mysql/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/mysql/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/mysql/LICENSE.md b/bitnami/mysql/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/mysql/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/mysqld-exporter/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/mysqld-exporter/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/mysqld-exporter/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/mysqld-exporter/.github/ISSUE_TEMPLATE/config.yml b/bitnami/mysqld-exporter/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/mysqld-exporter/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/mysqld-exporter/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/mysqld-exporter/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/mysqld-exporter/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/mysqld-exporter/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/mysqld-exporter/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/mysqld-exporter/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/mysqld-exporter/.github/workflows/stale.yml b/bitnami/mysqld-exporter/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/mysqld-exporter/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/mysqld-exporter/CODE_OF_CONDUCT.md b/bitnami/mysqld-exporter/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/mysqld-exporter/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/mysqld-exporter/CONTRIBUTING.md b/bitnami/mysqld-exporter/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/mysqld-exporter/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/mysqld-exporter/LICENSE.md b/bitnami/mysqld-exporter/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/mysqld-exporter/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/nats-exporter/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/nats-exporter/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/nats-exporter/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/nats-exporter/.github/ISSUE_TEMPLATE/config.yml b/bitnami/nats-exporter/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/nats-exporter/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/nats-exporter/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/nats-exporter/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/nats-exporter/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/nats-exporter/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/nats-exporter/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/nats-exporter/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/nats-exporter/.github/workflows/stale.yml b/bitnami/nats-exporter/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/nats-exporter/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/nats-exporter/CODE_OF_CONDUCT.md b/bitnami/nats-exporter/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/nats-exporter/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/nats-exporter/CONTRIBUTING.md b/bitnami/nats-exporter/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/nats-exporter/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/nats-exporter/LICENSE.md b/bitnami/nats-exporter/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/nats-exporter/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/nats/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/nats/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/nats/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/nats/.github/ISSUE_TEMPLATE/config.yml b/bitnami/nats/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/nats/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/nats/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/nats/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/nats/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/nats/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/nats/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/nats/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/nats/.github/workflows/stale.yml b/bitnami/nats/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/nats/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/nats/CODE_OF_CONDUCT.md b/bitnami/nats/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/nats/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/nats/CONTRIBUTING.md b/bitnami/nats/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/nats/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/nats/LICENSE.md b/bitnami/nats/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/nats/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/neo4j/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/neo4j/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/neo4j/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/neo4j/.github/ISSUE_TEMPLATE/config.yml b/bitnami/neo4j/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/neo4j/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/neo4j/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/neo4j/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/neo4j/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/neo4j/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/neo4j/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/neo4j/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/neo4j/.github/workflows/stale.yml b/bitnami/neo4j/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/neo4j/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/neo4j/CODE_OF_CONDUCT.md b/bitnami/neo4j/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/neo4j/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/neo4j/CONTRIBUTING.md b/bitnami/neo4j/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/neo4j/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/neo4j/LICENSE.md b/bitnami/neo4j/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/neo4j/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/nginx-exporter/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/nginx-exporter/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/nginx-exporter/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/nginx-exporter/.github/ISSUE_TEMPLATE/config.yml b/bitnami/nginx-exporter/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/nginx-exporter/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/nginx-exporter/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/nginx-exporter/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/nginx-exporter/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/nginx-exporter/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/nginx-exporter/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/nginx-exporter/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/nginx-exporter/.github/workflows/stale.yml b/bitnami/nginx-exporter/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/nginx-exporter/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/nginx-exporter/CODE_OF_CONDUCT.md b/bitnami/nginx-exporter/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/nginx-exporter/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/nginx-exporter/CONTRIBUTING.md b/bitnami/nginx-exporter/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/nginx-exporter/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/nginx-exporter/LICENSE.md b/bitnami/nginx-exporter/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/nginx-exporter/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/nginx-ingress-controller/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/nginx-ingress-controller/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/nginx-ingress-controller/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/nginx-ingress-controller/.github/ISSUE_TEMPLATE/config.yml b/bitnami/nginx-ingress-controller/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/nginx-ingress-controller/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/nginx-ingress-controller/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/nginx-ingress-controller/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/nginx-ingress-controller/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/nginx-ingress-controller/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/nginx-ingress-controller/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/nginx-ingress-controller/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/nginx-ingress-controller/.github/workflows/stale.yml b/bitnami/nginx-ingress-controller/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/nginx-ingress-controller/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/nginx-ingress-controller/CODE_OF_CONDUCT.md b/bitnami/nginx-ingress-controller/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/nginx-ingress-controller/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/nginx-ingress-controller/CONTRIBUTING.md b/bitnami/nginx-ingress-controller/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/nginx-ingress-controller/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/nginx-ingress-controller/LICENSE.md b/bitnami/nginx-ingress-controller/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/nginx-ingress-controller/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/nginx-intel/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/nginx-intel/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/nginx-intel/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/nginx-intel/.github/ISSUE_TEMPLATE/config.yml b/bitnami/nginx-intel/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/nginx-intel/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/nginx-intel/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/nginx-intel/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/nginx-intel/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/nginx-intel/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/nginx-intel/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/nginx-intel/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/nginx-intel/.github/workflows/stale.yml b/bitnami/nginx-intel/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/nginx-intel/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/nginx-intel/CODE_OF_CONDUCT.md b/bitnami/nginx-intel/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/nginx-intel/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/nginx-intel/CONTRIBUTING.md b/bitnami/nginx-intel/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/nginx-intel/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/nginx-intel/LICENSE.md b/bitnami/nginx-intel/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/nginx-intel/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/nginx-ldap-auth-daemon/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/nginx-ldap-auth-daemon/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/nginx-ldap-auth-daemon/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/nginx-ldap-auth-daemon/.github/ISSUE_TEMPLATE/config.yml b/bitnami/nginx-ldap-auth-daemon/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/nginx-ldap-auth-daemon/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/nginx-ldap-auth-daemon/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/nginx-ldap-auth-daemon/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/nginx-ldap-auth-daemon/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/nginx-ldap-auth-daemon/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/nginx-ldap-auth-daemon/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/nginx-ldap-auth-daemon/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/nginx-ldap-auth-daemon/.github/workflows/stale.yml b/bitnami/nginx-ldap-auth-daemon/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/nginx-ldap-auth-daemon/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/nginx-ldap-auth-daemon/CODE_OF_CONDUCT.md b/bitnami/nginx-ldap-auth-daemon/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/nginx-ldap-auth-daemon/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/nginx-ldap-auth-daemon/CONTRIBUTING.md b/bitnami/nginx-ldap-auth-daemon/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/nginx-ldap-auth-daemon/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/nginx-ldap-auth-daemon/LICENSE.md b/bitnami/nginx-ldap-auth-daemon/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/nginx-ldap-auth-daemon/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/nginx/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/nginx/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/nginx/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/nginx/.github/ISSUE_TEMPLATE/config.yml b/bitnami/nginx/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/nginx/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/nginx/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/nginx/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/nginx/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/nginx/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/nginx/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/nginx/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/nginx/.github/workflows/stale.yml b/bitnami/nginx/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/nginx/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/nginx/CODE_OF_CONDUCT.md b/bitnami/nginx/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/nginx/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/nginx/CONTRIBUTING.md b/bitnami/nginx/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/nginx/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/nginx/LICENSE.md b/bitnami/nginx/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/nginx/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/node-exporter/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/node-exporter/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/node-exporter/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/node-exporter/.github/ISSUE_TEMPLATE/config.yml b/bitnami/node-exporter/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/node-exporter/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/node-exporter/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/node-exporter/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/node-exporter/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/node-exporter/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/node-exporter/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/node-exporter/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/node-exporter/.github/workflows/stale.yml b/bitnami/node-exporter/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/node-exporter/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/node-exporter/CODE_OF_CONDUCT.md b/bitnami/node-exporter/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/node-exporter/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/node-exporter/CONTRIBUTING.md b/bitnami/node-exporter/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/node-exporter/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/node-exporter/LICENSE.md b/bitnami/node-exporter/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/node-exporter/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/node-snapshot/.github/ISSUE_TEMPLATE.md b/bitnami/node-snapshot/.github/ISSUE_TEMPLATE.md deleted file mode 100644 index 91afdfd82d31..000000000000 --- a/bitnami/node-snapshot/.github/ISSUE_TEMPLATE.md +++ /dev/null @@ -1,22 +0,0 @@ -**Description** - - - -**Steps to reproduce the issue:** - -1. [First Step] -2. [Second Step] -3. [and so on...] - -**Describe the results you received:** - - - -**Describe the results you expected:** - - - -**Additional information you deem important (e.g. issue happens only occasionally, environment details, etc.):** - - - diff --git a/bitnami/node-snapshot/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/node-snapshot/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/node-snapshot/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/node-snapshot/.github/workflows/stale.yml b/bitnami/node-snapshot/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/node-snapshot/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/node-snapshot/CODE_OF_CONDUCT.md b/bitnami/node-snapshot/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/node-snapshot/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/node-snapshot/CONTRIBUTING.md b/bitnami/node-snapshot/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/node-snapshot/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/node-snapshot/LICENSE.md b/bitnami/node-snapshot/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/node-snapshot/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/node/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/node/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/node/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/node/.github/ISSUE_TEMPLATE/config.yml b/bitnami/node/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/node/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/node/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/node/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/node/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/node/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/node/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/node/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/node/.github/workflows/stale.yml b/bitnami/node/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/node/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/node/CODE_OF_CONDUCT.md b/bitnami/node/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/node/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/node/CONTRIBUTING.md b/bitnami/node/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/node/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/node/LICENSE.md b/bitnami/node/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/node/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/oauth2-proxy/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/oauth2-proxy/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/oauth2-proxy/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/oauth2-proxy/.github/ISSUE_TEMPLATE/config.yml b/bitnami/oauth2-proxy/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/oauth2-proxy/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/oauth2-proxy/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/oauth2-proxy/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/oauth2-proxy/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/oauth2-proxy/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/oauth2-proxy/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/oauth2-proxy/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/oauth2-proxy/.github/workflows/stale.yml b/bitnami/oauth2-proxy/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/oauth2-proxy/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/oauth2-proxy/CODE_OF_CONDUCT.md b/bitnami/oauth2-proxy/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/oauth2-proxy/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/oauth2-proxy/CONTRIBUTING.md b/bitnami/oauth2-proxy/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/oauth2-proxy/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/oauth2-proxy/LICENSE.md b/bitnami/oauth2-proxy/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/oauth2-proxy/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/odoo/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/odoo/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/odoo/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/odoo/.github/ISSUE_TEMPLATE/config.yml b/bitnami/odoo/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/odoo/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/odoo/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/odoo/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/odoo/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/odoo/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/odoo/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/odoo/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/odoo/.github/workflows/stale.yml b/bitnami/odoo/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/odoo/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/odoo/CODE_OF_CONDUCT.md b/bitnami/odoo/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/odoo/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/odoo/CONTRIBUTING.md b/bitnami/odoo/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/odoo/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/odoo/LICENSE.md b/bitnami/odoo/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/odoo/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/open-service-broker-azure/.github/ISSUE_TEMPLATE.md b/bitnami/open-service-broker-azure/.github/ISSUE_TEMPLATE.md deleted file mode 100644 index 91afdfd82d31..000000000000 --- a/bitnami/open-service-broker-azure/.github/ISSUE_TEMPLATE.md +++ /dev/null @@ -1,22 +0,0 @@ -**Description** - - - -**Steps to reproduce the issue:** - -1. [First Step] -2. [Second Step] -3. [and so on...] - -**Describe the results you received:** - - - -**Describe the results you expected:** - - - -**Additional information you deem important (e.g. issue happens only occasionally, environment details, etc.):** - - - diff --git a/bitnami/open-service-broker-azure/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/open-service-broker-azure/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/open-service-broker-azure/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/open-service-broker-azure/.github/workflows/stale.yml b/bitnami/open-service-broker-azure/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/open-service-broker-azure/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/open-service-broker-azure/CODE_OF_CONDUCT.md b/bitnami/open-service-broker-azure/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/open-service-broker-azure/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/open-service-broker-azure/CONTRIBUTING.md b/bitnami/open-service-broker-azure/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/open-service-broker-azure/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/open-service-broker-azure/LICENSE.md b/bitnami/open-service-broker-azure/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/open-service-broker-azure/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/opencart/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/opencart/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/opencart/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/opencart/.github/ISSUE_TEMPLATE/config.yml b/bitnami/opencart/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/opencart/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/opencart/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/opencart/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/opencart/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/opencart/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/opencart/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/opencart/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/opencart/.github/workflows/stale.yml b/bitnami/opencart/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/opencart/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/opencart/CODE_OF_CONDUCT.md b/bitnami/opencart/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/opencart/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/opencart/CONTRIBUTING.md b/bitnami/opencart/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/opencart/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/opencart/LICENSE.md b/bitnami/opencart/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/opencart/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/openldap/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/openldap/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/openldap/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/openldap/.github/ISSUE_TEMPLATE/config.yml b/bitnami/openldap/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/openldap/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/openldap/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/openldap/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/openldap/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/openldap/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/openldap/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/openldap/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/openldap/.github/workflows/stale.yml b/bitnami/openldap/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/openldap/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/openldap/CODE_OF_CONDUCT.md b/bitnami/openldap/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/openldap/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/openldap/CONTRIBUTING.md b/bitnami/openldap/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/openldap/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/openldap/LICENSE.md b/bitnami/openldap/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/openldap/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/openresty/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/openresty/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/openresty/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/openresty/.github/ISSUE_TEMPLATE/config.yml b/bitnami/openresty/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/openresty/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/openresty/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/openresty/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/openresty/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/openresty/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/openresty/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/openresty/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/openresty/.github/workflows/stale.yml b/bitnami/openresty/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/openresty/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/openresty/CODE_OF_CONDUCT.md b/bitnami/openresty/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/openresty/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/openresty/CONTRIBUTING.md b/bitnami/openresty/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/openresty/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/openresty/LICENSE.md b/bitnami/openresty/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/openresty/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/orangehrm/.github/ISSUE_TEMPLATE.md b/bitnami/orangehrm/.github/ISSUE_TEMPLATE.md deleted file mode 100644 index 91afdfd82d31..000000000000 --- a/bitnami/orangehrm/.github/ISSUE_TEMPLATE.md +++ /dev/null @@ -1,22 +0,0 @@ -**Description** - - - -**Steps to reproduce the issue:** - -1. [First Step] -2. [Second Step] -3. [and so on...] - -**Describe the results you received:** - - - -**Describe the results you expected:** - - - -**Additional information you deem important (e.g. issue happens only occasionally, environment details, etc.):** - - - diff --git a/bitnami/orangehrm/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/orangehrm/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/orangehrm/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/orangehrm/.github/workflows/stale.yml b/bitnami/orangehrm/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/orangehrm/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/orangehrm/CODE_OF_CONDUCT.md b/bitnami/orangehrm/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/orangehrm/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/orangehrm/CONTRIBUTING.md b/bitnami/orangehrm/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/orangehrm/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/orangehrm/LICENSE.md b/bitnami/orangehrm/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/orangehrm/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/oras/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/oras/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/oras/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/oras/.github/ISSUE_TEMPLATE/config.yml b/bitnami/oras/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/oras/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/oras/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/oras/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/oras/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/oras/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/oras/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/oras/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/oras/.github/workflows/stale.yml b/bitnami/oras/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/oras/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/oras/CODE_OF_CONDUCT.md b/bitnami/oras/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/oras/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/oras/CONTRIBUTING.md b/bitnami/oras/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/oras/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/oras/LICENSE.md b/bitnami/oras/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/oras/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/osclass/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/osclass/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/osclass/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/osclass/.github/ISSUE_TEMPLATE/config.yml b/bitnami/osclass/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/osclass/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/osclass/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/osclass/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/osclass/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/osclass/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/osclass/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/osclass/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/osclass/.github/workflows/stale.yml b/bitnami/osclass/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/osclass/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/osclass/CODE_OF_CONDUCT.md b/bitnami/osclass/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/osclass/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/osclass/CONTRIBUTING.md b/bitnami/osclass/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/osclass/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/osclass/LICENSE.md b/bitnami/osclass/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/osclass/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/owncloud/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/owncloud/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/owncloud/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/owncloud/.github/ISSUE_TEMPLATE/config.yml b/bitnami/owncloud/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/owncloud/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/owncloud/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/owncloud/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/owncloud/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/owncloud/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/owncloud/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/owncloud/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/owncloud/.github/workflows/stale.yml b/bitnami/owncloud/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/owncloud/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/owncloud/CODE_OF_CONDUCT.md b/bitnami/owncloud/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/owncloud/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/owncloud/CONTRIBUTING.md b/bitnami/owncloud/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/owncloud/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/owncloud/LICENSE.md b/bitnami/owncloud/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/owncloud/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/parse-dashboard/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/parse-dashboard/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/parse-dashboard/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/parse-dashboard/.github/ISSUE_TEMPLATE/config.yml b/bitnami/parse-dashboard/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/parse-dashboard/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/parse-dashboard/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/parse-dashboard/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/parse-dashboard/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/parse-dashboard/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/parse-dashboard/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/parse-dashboard/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/parse-dashboard/.github/workflows/stale.yml b/bitnami/parse-dashboard/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/parse-dashboard/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/parse-dashboard/CODE_OF_CONDUCT.md b/bitnami/parse-dashboard/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/parse-dashboard/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/parse-dashboard/CONTRIBUTING.md b/bitnami/parse-dashboard/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/parse-dashboard/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/parse-dashboard/LICENSE.md b/bitnami/parse-dashboard/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/parse-dashboard/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/parse/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/parse/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/parse/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/parse/.github/ISSUE_TEMPLATE/config.yml b/bitnami/parse/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/parse/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/parse/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/parse/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/parse/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/parse/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/parse/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/parse/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/parse/.github/workflows/stale.yml b/bitnami/parse/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/parse/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/parse/CODE_OF_CONDUCT.md b/bitnami/parse/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/parse/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/parse/CONTRIBUTING.md b/bitnami/parse/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/parse/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/parse/LICENSE.md b/bitnami/parse/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/parse/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/percona-xtrabackup/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/percona-xtrabackup/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/percona-xtrabackup/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/percona-xtrabackup/.github/ISSUE_TEMPLATE/config.yml b/bitnami/percona-xtrabackup/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/percona-xtrabackup/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/percona-xtrabackup/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/percona-xtrabackup/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/percona-xtrabackup/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/percona-xtrabackup/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/percona-xtrabackup/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/percona-xtrabackup/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/percona-xtrabackup/.github/workflows/stale.yml b/bitnami/percona-xtrabackup/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/percona-xtrabackup/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/percona-xtrabackup/CODE_OF_CONDUCT.md b/bitnami/percona-xtrabackup/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/percona-xtrabackup/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/percona-xtrabackup/CONTRIBUTING.md b/bitnami/percona-xtrabackup/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/percona-xtrabackup/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/percona-xtrabackup/LICENSE.md b/bitnami/percona-xtrabackup/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/percona-xtrabackup/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/pgbouncer/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/pgbouncer/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/pgbouncer/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/pgbouncer/.github/ISSUE_TEMPLATE/config.yml b/bitnami/pgbouncer/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/pgbouncer/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/pgbouncer/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/pgbouncer/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/pgbouncer/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/pgbouncer/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/pgbouncer/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/pgbouncer/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/pgbouncer/.github/workflows/stale.yml b/bitnami/pgbouncer/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/pgbouncer/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/pgbouncer/CODE_OF_CONDUCT.md b/bitnami/pgbouncer/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/pgbouncer/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/pgbouncer/CONTRIBUTING.md b/bitnami/pgbouncer/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/pgbouncer/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/pgbouncer/LICENSE.md b/bitnami/pgbouncer/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/pgbouncer/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/pgpool/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/pgpool/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/pgpool/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/pgpool/.github/ISSUE_TEMPLATE/config.yml b/bitnami/pgpool/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/pgpool/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/pgpool/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/pgpool/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/pgpool/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/pgpool/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/pgpool/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/pgpool/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/pgpool/.github/workflows/stale.yml b/bitnami/pgpool/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/pgpool/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/pgpool/CODE_OF_CONDUCT.md b/bitnami/pgpool/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/pgpool/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/pgpool/CONTRIBUTING.md b/bitnami/pgpool/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/pgpool/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/pgpool/LICENSE.md b/bitnami/pgpool/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/pgpool/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/php-fpm/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/php-fpm/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/php-fpm/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/php-fpm/.github/ISSUE_TEMPLATE/config.yml b/bitnami/php-fpm/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/php-fpm/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/php-fpm/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/php-fpm/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/php-fpm/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/php-fpm/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/php-fpm/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/php-fpm/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/php-fpm/.github/workflows/stale.yml b/bitnami/php-fpm/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/php-fpm/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/php-fpm/CODE_OF_CONDUCT.md b/bitnami/php-fpm/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/php-fpm/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/php-fpm/CONTRIBUTING.md b/bitnami/php-fpm/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/php-fpm/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/php-fpm/LICENSE.md b/bitnami/php-fpm/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/php-fpm/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/phpbb/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/phpbb/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/phpbb/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/phpbb/.github/ISSUE_TEMPLATE/config.yml b/bitnami/phpbb/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/phpbb/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/phpbb/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/phpbb/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/phpbb/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/phpbb/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/phpbb/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/phpbb/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/phpbb/.github/workflows/stale.yml b/bitnami/phpbb/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/phpbb/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/phpbb/CODE_OF_CONDUCT.md b/bitnami/phpbb/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/phpbb/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/phpbb/CONTRIBUTING.md b/bitnami/phpbb/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/phpbb/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/phpbb/LICENSE.md b/bitnami/phpbb/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/phpbb/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/phpmyadmin/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/phpmyadmin/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/phpmyadmin/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/phpmyadmin/.github/ISSUE_TEMPLATE/config.yml b/bitnami/phpmyadmin/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/phpmyadmin/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/phpmyadmin/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/phpmyadmin/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/phpmyadmin/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/phpmyadmin/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/phpmyadmin/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/phpmyadmin/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/phpmyadmin/.github/workflows/stale.yml b/bitnami/phpmyadmin/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/phpmyadmin/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/phpmyadmin/CODE_OF_CONDUCT.md b/bitnami/phpmyadmin/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/phpmyadmin/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/phpmyadmin/CONTRIBUTING.md b/bitnami/phpmyadmin/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/phpmyadmin/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/phpmyadmin/LICENSE.md b/bitnami/phpmyadmin/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/phpmyadmin/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/phppgadmin/.github/ISSUE_TEMPLATE.md b/bitnami/phppgadmin/.github/ISSUE_TEMPLATE.md deleted file mode 100644 index 91afdfd82d31..000000000000 --- a/bitnami/phppgadmin/.github/ISSUE_TEMPLATE.md +++ /dev/null @@ -1,22 +0,0 @@ -**Description** - - - -**Steps to reproduce the issue:** - -1. [First Step] -2. [Second Step] -3. [and so on...] - -**Describe the results you received:** - - - -**Describe the results you expected:** - - - -**Additional information you deem important (e.g. issue happens only occasionally, environment details, etc.):** - - - diff --git a/bitnami/phppgadmin/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/phppgadmin/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/phppgadmin/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/phppgadmin/.github/workflows/stale.yml b/bitnami/phppgadmin/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/phppgadmin/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/phppgadmin/CODE_OF_CONDUCT.md b/bitnami/phppgadmin/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/phppgadmin/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/phppgadmin/CONTRIBUTING.md b/bitnami/phppgadmin/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/phppgadmin/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/phppgadmin/LICENSE.md b/bitnami/phppgadmin/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/phppgadmin/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/postgres-exporter/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/postgres-exporter/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/postgres-exporter/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/postgres-exporter/.github/ISSUE_TEMPLATE/config.yml b/bitnami/postgres-exporter/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/postgres-exporter/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/postgres-exporter/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/postgres-exporter/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/postgres-exporter/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/postgres-exporter/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/postgres-exporter/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/postgres-exporter/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/postgres-exporter/.github/workflows/stale.yml b/bitnami/postgres-exporter/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/postgres-exporter/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/postgres-exporter/CODE_OF_CONDUCT.md b/bitnami/postgres-exporter/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/postgres-exporter/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/postgres-exporter/CONTRIBUTING.md b/bitnami/postgres-exporter/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/postgres-exporter/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/postgres-exporter/LICENSE.md b/bitnami/postgres-exporter/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/postgres-exporter/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/postgresql-repmgr/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/postgresql-repmgr/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/postgresql-repmgr/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/postgresql-repmgr/.github/ISSUE_TEMPLATE/config.yml b/bitnami/postgresql-repmgr/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/postgresql-repmgr/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/postgresql-repmgr/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/postgresql-repmgr/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/postgresql-repmgr/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/postgresql-repmgr/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/postgresql-repmgr/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/postgresql-repmgr/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/postgresql-repmgr/.github/workflows/stale.yml b/bitnami/postgresql-repmgr/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/postgresql-repmgr/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/postgresql-repmgr/CODE_OF_CONDUCT.md b/bitnami/postgresql-repmgr/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/postgresql-repmgr/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/postgresql-repmgr/CONTRIBUTING.md b/bitnami/postgresql-repmgr/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/postgresql-repmgr/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/postgresql-repmgr/LICENSE.md b/bitnami/postgresql-repmgr/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/postgresql-repmgr/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/postgresql/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/postgresql/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/postgresql/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/postgresql/.github/ISSUE_TEMPLATE/config.yml b/bitnami/postgresql/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/postgresql/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/postgresql/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/postgresql/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/postgresql/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/postgresql/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/postgresql/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/postgresql/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/postgresql/.github/workflows/stale.yml b/bitnami/postgresql/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/postgresql/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/postgresql/CODE_OF_CONDUCT.md b/bitnami/postgresql/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/postgresql/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/postgresql/CONTRIBUTING.md b/bitnami/postgresql/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/postgresql/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/postgresql/LICENSE.md b/bitnami/postgresql/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/postgresql/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/prestashop/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/prestashop/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/prestashop/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/prestashop/.github/ISSUE_TEMPLATE/config.yml b/bitnami/prestashop/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/prestashop/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/prestashop/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/prestashop/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/prestashop/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/prestashop/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/prestashop/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/prestashop/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/prestashop/.github/workflows/stale.yml b/bitnami/prestashop/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/prestashop/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/prestashop/CODE_OF_CONDUCT.md b/bitnami/prestashop/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/prestashop/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/prestashop/CONTRIBUTING.md b/bitnami/prestashop/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/prestashop/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/prestashop/LICENSE.md b/bitnami/prestashop/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/prestashop/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/prometheus-operator/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/prometheus-operator/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/prometheus-operator/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/prometheus-operator/.github/ISSUE_TEMPLATE/config.yml b/bitnami/prometheus-operator/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/prometheus-operator/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/prometheus-operator/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/prometheus-operator/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/prometheus-operator/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/prometheus-operator/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/prometheus-operator/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/prometheus-operator/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/prometheus-operator/.github/workflows/stale.yml b/bitnami/prometheus-operator/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/prometheus-operator/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/prometheus-operator/CODE_OF_CONDUCT.md b/bitnami/prometheus-operator/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/prometheus-operator/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/prometheus-operator/CONTRIBUTING.md b/bitnami/prometheus-operator/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/prometheus-operator/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/prometheus-operator/LICENSE.md b/bitnami/prometheus-operator/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/prometheus-operator/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/prometheus-rsocket-proxy/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/prometheus-rsocket-proxy/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/prometheus-rsocket-proxy/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/prometheus-rsocket-proxy/.github/ISSUE_TEMPLATE/config.yml b/bitnami/prometheus-rsocket-proxy/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/prometheus-rsocket-proxy/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/prometheus-rsocket-proxy/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/prometheus-rsocket-proxy/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/prometheus-rsocket-proxy/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/prometheus-rsocket-proxy/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/prometheus-rsocket-proxy/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/prometheus-rsocket-proxy/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/prometheus-rsocket-proxy/.github/workflows/stale.yml b/bitnami/prometheus-rsocket-proxy/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/prometheus-rsocket-proxy/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/prometheus-rsocket-proxy/CODE_OF_CONDUCT.md b/bitnami/prometheus-rsocket-proxy/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/prometheus-rsocket-proxy/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/prometheus-rsocket-proxy/CONTRIBUTING.md b/bitnami/prometheus-rsocket-proxy/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/prometheus-rsocket-proxy/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/prometheus-rsocket-proxy/LICENSE.md b/bitnami/prometheus-rsocket-proxy/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/prometheus-rsocket-proxy/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/prometheus/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/prometheus/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/prometheus/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/prometheus/.github/ISSUE_TEMPLATE/config.yml b/bitnami/prometheus/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/prometheus/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/prometheus/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/prometheus/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/prometheus/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/prometheus/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/prometheus/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/prometheus/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/prometheus/.github/workflows/stale.yml b/bitnami/prometheus/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/prometheus/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/prometheus/CODE_OF_CONDUCT.md b/bitnami/prometheus/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/prometheus/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/prometheus/CONTRIBUTING.md b/bitnami/prometheus/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/prometheus/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/prometheus/LICENSE.md b/bitnami/prometheus/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/prometheus/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/pushgateway/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/pushgateway/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/pushgateway/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/pushgateway/.github/ISSUE_TEMPLATE/config.yml b/bitnami/pushgateway/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/pushgateway/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/pushgateway/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/pushgateway/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/pushgateway/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/pushgateway/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/pushgateway/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/pushgateway/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/pushgateway/.github/workflows/stale.yml b/bitnami/pushgateway/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/pushgateway/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/pushgateway/CODE_OF_CONDUCT.md b/bitnami/pushgateway/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/pushgateway/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/pushgateway/CONTRIBUTING.md b/bitnami/pushgateway/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/pushgateway/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/pushgateway/LICENSE.md b/bitnami/pushgateway/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/pushgateway/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/python-snapshot/.github/ISSUE_TEMPLATE.md b/bitnami/python-snapshot/.github/ISSUE_TEMPLATE.md deleted file mode 100644 index 91afdfd82d31..000000000000 --- a/bitnami/python-snapshot/.github/ISSUE_TEMPLATE.md +++ /dev/null @@ -1,22 +0,0 @@ -**Description** - - - -**Steps to reproduce the issue:** - -1. [First Step] -2. [Second Step] -3. [and so on...] - -**Describe the results you received:** - - - -**Describe the results you expected:** - - - -**Additional information you deem important (e.g. issue happens only occasionally, environment details, etc.):** - - - diff --git a/bitnami/python-snapshot/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/python-snapshot/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/python-snapshot/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/python-snapshot/.github/workflows/stale.yml b/bitnami/python-snapshot/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/python-snapshot/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/python-snapshot/CODE_OF_CONDUCT.md b/bitnami/python-snapshot/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/python-snapshot/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/python-snapshot/CONTRIBUTING.md b/bitnami/python-snapshot/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/python-snapshot/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/python-snapshot/LICENSE.md b/bitnami/python-snapshot/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/python-snapshot/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/python/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/python/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/python/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/python/.github/ISSUE_TEMPLATE/config.yml b/bitnami/python/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/python/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/python/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/python/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/python/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/python/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/python/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/python/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/python/.github/workflows/stale.yml b/bitnami/python/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/python/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/python/CODE_OF_CONDUCT.md b/bitnami/python/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/python/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/python/CONTRIBUTING.md b/bitnami/python/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/python/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/python/LICENSE.md b/bitnami/python/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/python/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/pytorch/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/pytorch/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/pytorch/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/pytorch/.github/ISSUE_TEMPLATE/config.yml b/bitnami/pytorch/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/pytorch/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/pytorch/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/pytorch/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/pytorch/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/pytorch/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/pytorch/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/pytorch/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/pytorch/.github/workflows/stale.yml b/bitnami/pytorch/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/pytorch/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/pytorch/CODE_OF_CONDUCT.md b/bitnami/pytorch/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/pytorch/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/pytorch/CONTRIBUTING.md b/bitnami/pytorch/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/pytorch/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/pytorch/LICENSE.md b/bitnami/pytorch/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/pytorch/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/rabbitmq-cluster-operator/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/rabbitmq-cluster-operator/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/rabbitmq-cluster-operator/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/rabbitmq-cluster-operator/.github/ISSUE_TEMPLATE/config.yml b/bitnami/rabbitmq-cluster-operator/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/rabbitmq-cluster-operator/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/rabbitmq-cluster-operator/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/rabbitmq-cluster-operator/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/rabbitmq-cluster-operator/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/rabbitmq-cluster-operator/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/rabbitmq-cluster-operator/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/rabbitmq-cluster-operator/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/rabbitmq-cluster-operator/.github/workflows/stale.yml b/bitnami/rabbitmq-cluster-operator/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/rabbitmq-cluster-operator/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/rabbitmq-cluster-operator/CODE_OF_CONDUCT.md b/bitnami/rabbitmq-cluster-operator/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/rabbitmq-cluster-operator/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/rabbitmq-cluster-operator/CONTRIBUTING.md b/bitnami/rabbitmq-cluster-operator/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/rabbitmq-cluster-operator/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/rabbitmq-cluster-operator/LICENSE.md b/bitnami/rabbitmq-cluster-operator/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/rabbitmq-cluster-operator/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/rabbitmq/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/rabbitmq/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/rabbitmq/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/rabbitmq/.github/ISSUE_TEMPLATE/config.yml b/bitnami/rabbitmq/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/rabbitmq/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/rabbitmq/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/rabbitmq/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/rabbitmq/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/rabbitmq/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/rabbitmq/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/rabbitmq/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/rabbitmq/.github/workflows/stale.yml b/bitnami/rabbitmq/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/rabbitmq/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/rabbitmq/CODE_OF_CONDUCT.md b/bitnami/rabbitmq/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/rabbitmq/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/rabbitmq/CONTRIBUTING.md b/bitnami/rabbitmq/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/rabbitmq/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/rabbitmq/LICENSE.md b/bitnami/rabbitmq/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/rabbitmq/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/rails/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/rails/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/rails/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/rails/.github/ISSUE_TEMPLATE/config.yml b/bitnami/rails/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/rails/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/rails/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/rails/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/rails/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/rails/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/rails/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/rails/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/rails/.github/workflows/stale.yml b/bitnami/rails/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/rails/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/rails/CODE_OF_CONDUCT.md b/bitnami/rails/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/rails/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/rails/CONTRIBUTING.md b/bitnami/rails/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/rails/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/rails/LICENSE.md b/bitnami/rails/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/rails/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/rclone/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/rclone/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/rclone/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/rclone/.github/ISSUE_TEMPLATE/config.yml b/bitnami/rclone/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/rclone/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/rclone/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/rclone/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/rclone/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/rclone/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/rclone/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/rclone/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/rclone/.github/workflows/stale.yml b/bitnami/rclone/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/rclone/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/rclone/CODE_OF_CONDUCT.md b/bitnami/rclone/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/rclone/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/rclone/CONTRIBUTING.md b/bitnami/rclone/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/rclone/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/rclone/LICENSE.md b/bitnami/rclone/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/rclone/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/redis-cluster/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/redis-cluster/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/redis-cluster/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/redis-cluster/.github/ISSUE_TEMPLATE/config.yml b/bitnami/redis-cluster/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/redis-cluster/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/redis-cluster/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/redis-cluster/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/redis-cluster/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/redis-cluster/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/redis-cluster/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/redis-cluster/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/redis-cluster/.github/workflows/stale.yml b/bitnami/redis-cluster/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/redis-cluster/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/redis-cluster/CODE_OF_CONDUCT.md b/bitnami/redis-cluster/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/redis-cluster/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/redis-cluster/CONTRIBUTING.md b/bitnami/redis-cluster/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/redis-cluster/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/redis-cluster/LICENSE.md b/bitnami/redis-cluster/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/redis-cluster/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/redis-exporter/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/redis-exporter/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/redis-exporter/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/redis-exporter/.github/ISSUE_TEMPLATE/config.yml b/bitnami/redis-exporter/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/redis-exporter/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/redis-exporter/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/redis-exporter/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/redis-exporter/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/redis-exporter/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/redis-exporter/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/redis-exporter/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/redis-exporter/.github/workflows/stale.yml b/bitnami/redis-exporter/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/redis-exporter/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/redis-exporter/CODE_OF_CONDUCT.md b/bitnami/redis-exporter/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/redis-exporter/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/redis-exporter/CONTRIBUTING.md b/bitnami/redis-exporter/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/redis-exporter/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/redis-exporter/LICENSE.md b/bitnami/redis-exporter/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/redis-exporter/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/redis-sentinel/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/redis-sentinel/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/redis-sentinel/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/redis-sentinel/.github/ISSUE_TEMPLATE/config.yml b/bitnami/redis-sentinel/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/redis-sentinel/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/redis-sentinel/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/redis-sentinel/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/redis-sentinel/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/redis-sentinel/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/redis-sentinel/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/redis-sentinel/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/redis-sentinel/.github/workflows/stale.yml b/bitnami/redis-sentinel/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/redis-sentinel/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/redis-sentinel/CODE_OF_CONDUCT.md b/bitnami/redis-sentinel/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/redis-sentinel/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/redis-sentinel/CONTRIBUTING.md b/bitnami/redis-sentinel/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/redis-sentinel/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/redis-sentinel/LICENSE.md b/bitnami/redis-sentinel/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/redis-sentinel/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/redis/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/redis/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/redis/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/redis/.github/ISSUE_TEMPLATE/config.yml b/bitnami/redis/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/redis/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/redis/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/redis/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/redis/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/redis/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/redis/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/redis/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/redis/.github/workflows/stale.yml b/bitnami/redis/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/redis/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/redis/CODE_OF_CONDUCT.md b/bitnami/redis/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/redis/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/redis/CONTRIBUTING.md b/bitnami/redis/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/redis/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/redis/LICENSE.md b/bitnami/redis/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/redis/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/redmine/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/redmine/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/redmine/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/redmine/.github/ISSUE_TEMPLATE/config.yml b/bitnami/redmine/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/redmine/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/redmine/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/redmine/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/redmine/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/redmine/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/redmine/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/redmine/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/redmine/.github/workflows/stale.yml b/bitnami/redmine/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/redmine/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/redmine/CODE_OF_CONDUCT.md b/bitnami/redmine/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/redmine/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/redmine/CONTRIBUTING.md b/bitnami/redmine/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/redmine/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/redmine/LICENSE.md b/bitnami/redmine/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/redmine/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/reportserver/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/reportserver/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/reportserver/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/reportserver/.github/ISSUE_TEMPLATE/config.yml b/bitnami/reportserver/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/reportserver/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/reportserver/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/reportserver/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/reportserver/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/reportserver/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/reportserver/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/reportserver/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/reportserver/.github/workflows/stale.yml b/bitnami/reportserver/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/reportserver/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/reportserver/CODE_OF_CONDUCT.md b/bitnami/reportserver/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/reportserver/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/reportserver/CONTRIBUTING.md b/bitnami/reportserver/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/reportserver/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/reportserver/LICENSE.md b/bitnami/reportserver/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/reportserver/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/reportserverenterprise/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/reportserverenterprise/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/reportserverenterprise/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/reportserverenterprise/.github/ISSUE_TEMPLATE/config.yml b/bitnami/reportserverenterprise/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/reportserverenterprise/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/reportserverenterprise/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/reportserverenterprise/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/reportserverenterprise/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/reportserverenterprise/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/reportserverenterprise/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/reportserverenterprise/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/reportserverenterprise/.github/workflows/stale.yml b/bitnami/reportserverenterprise/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/reportserverenterprise/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/reportserverenterprise/CODE_OF_CONDUCT.md b/bitnami/reportserverenterprise/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/reportserverenterprise/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/reportserverenterprise/CONTRIBUTING.md b/bitnami/reportserverenterprise/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/reportserverenterprise/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/reportserverenterprise/LICENSE.md b/bitnami/reportserverenterprise/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/reportserverenterprise/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/rmq-default-credential-updater/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/rmq-default-credential-updater/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/rmq-default-credential-updater/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/rmq-default-credential-updater/.github/ISSUE_TEMPLATE/config.yml b/bitnami/rmq-default-credential-updater/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/rmq-default-credential-updater/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/rmq-default-credential-updater/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/rmq-default-credential-updater/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/rmq-default-credential-updater/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/rmq-default-credential-updater/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/rmq-default-credential-updater/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/rmq-default-credential-updater/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/rmq-default-credential-updater/.github/workflows/stale.yml b/bitnami/rmq-default-credential-updater/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/rmq-default-credential-updater/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/rmq-default-credential-updater/CODE_OF_CONDUCT.md b/bitnami/rmq-default-credential-updater/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/rmq-default-credential-updater/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/rmq-default-credential-updater/CONTRIBUTING.md b/bitnami/rmq-default-credential-updater/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/rmq-default-credential-updater/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/rmq-default-credential-updater/LICENSE.md b/bitnami/rmq-default-credential-updater/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/rmq-default-credential-updater/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/rmq-messaging-topology-operator/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/rmq-messaging-topology-operator/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/rmq-messaging-topology-operator/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/rmq-messaging-topology-operator/.github/ISSUE_TEMPLATE/config.yml b/bitnami/rmq-messaging-topology-operator/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/rmq-messaging-topology-operator/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/rmq-messaging-topology-operator/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/rmq-messaging-topology-operator/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/rmq-messaging-topology-operator/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/rmq-messaging-topology-operator/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/rmq-messaging-topology-operator/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/rmq-messaging-topology-operator/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/rmq-messaging-topology-operator/.github/workflows/stale.yml b/bitnami/rmq-messaging-topology-operator/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/rmq-messaging-topology-operator/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/rmq-messaging-topology-operator/CODE_OF_CONDUCT.md b/bitnami/rmq-messaging-topology-operator/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/rmq-messaging-topology-operator/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/rmq-messaging-topology-operator/CONTRIBUTING.md b/bitnami/rmq-messaging-topology-operator/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/rmq-messaging-topology-operator/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/rmq-messaging-topology-operator/LICENSE.md b/bitnami/rmq-messaging-topology-operator/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/rmq-messaging-topology-operator/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/ruby/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/ruby/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/ruby/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/ruby/.github/ISSUE_TEMPLATE/config.yml b/bitnami/ruby/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/ruby/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/ruby/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/ruby/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/ruby/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/ruby/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/ruby/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/ruby/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/ruby/.github/workflows/stale.yml b/bitnami/ruby/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/ruby/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/ruby/CODE_OF_CONDUCT.md b/bitnami/ruby/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/ruby/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/ruby/CONTRIBUTING.md b/bitnami/ruby/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/ruby/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/ruby/LICENSE.md b/bitnami/ruby/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/ruby/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/service-catalog/.github/ISSUE_TEMPLATE.md b/bitnami/service-catalog/.github/ISSUE_TEMPLATE.md deleted file mode 100644 index 91afdfd82d31..000000000000 --- a/bitnami/service-catalog/.github/ISSUE_TEMPLATE.md +++ /dev/null @@ -1,22 +0,0 @@ -**Description** - - - -**Steps to reproduce the issue:** - -1. [First Step] -2. [Second Step] -3. [and so on...] - -**Describe the results you received:** - - - -**Describe the results you expected:** - - - -**Additional information you deem important (e.g. issue happens only occasionally, environment details, etc.):** - - - diff --git a/bitnami/service-catalog/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/service-catalog/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/service-catalog/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/service-catalog/.github/workflows/stale.yml b/bitnami/service-catalog/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/service-catalog/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/service-catalog/CODE_OF_CONDUCT.md b/bitnami/service-catalog/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/service-catalog/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/service-catalog/CONTRIBUTING.md b/bitnami/service-catalog/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/service-catalog/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/service-catalog/LICENSE.md b/bitnami/service-catalog/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/service-catalog/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/solr/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/solr/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/solr/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/solr/.github/ISSUE_TEMPLATE/config.yml b/bitnami/solr/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/solr/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/solr/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/solr/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/solr/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/solr/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/solr/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/solr/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/solr/.github/workflows/stale.yml b/bitnami/solr/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/solr/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/solr/CODE_OF_CONDUCT.md b/bitnami/solr/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/solr/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/solr/CONTRIBUTING.md b/bitnami/solr/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/solr/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/solr/LICENSE.md b/bitnami/solr/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/solr/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/sonarqube/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/sonarqube/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/sonarqube/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/sonarqube/.github/ISSUE_TEMPLATE/config.yml b/bitnami/sonarqube/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/sonarqube/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/sonarqube/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/sonarqube/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/sonarqube/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/sonarqube/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/sonarqube/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/sonarqube/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/sonarqube/.github/workflows/stale.yml b/bitnami/sonarqube/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/sonarqube/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/sonarqube/CODE_OF_CONDUCT.md b/bitnami/sonarqube/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/sonarqube/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/sonarqube/CONTRIBUTING.md b/bitnami/sonarqube/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/sonarqube/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/sonarqube/LICENSE.md b/bitnami/sonarqube/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/sonarqube/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/spark/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/spark/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/spark/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/spark/.github/ISSUE_TEMPLATE/config.yml b/bitnami/spark/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/spark/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/spark/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/spark/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/spark/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/spark/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/spark/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/spark/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/spark/.github/workflows/stale.yml b/bitnami/spark/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/spark/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/spark/CODE_OF_CONDUCT.md b/bitnami/spark/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/spark/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/spark/CONTRIBUTING.md b/bitnami/spark/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/spark/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/spark/LICENSE.md b/bitnami/spark/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/spark/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/spring-cloud-dataflow-composed-task-runner/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/spring-cloud-dataflow-composed-task-runner/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/spring-cloud-dataflow-composed-task-runner/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/spring-cloud-dataflow-composed-task-runner/.github/ISSUE_TEMPLATE/config.yml b/bitnami/spring-cloud-dataflow-composed-task-runner/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/spring-cloud-dataflow-composed-task-runner/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/spring-cloud-dataflow-composed-task-runner/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/spring-cloud-dataflow-composed-task-runner/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/spring-cloud-dataflow-composed-task-runner/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/spring-cloud-dataflow-composed-task-runner/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/spring-cloud-dataflow-composed-task-runner/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/spring-cloud-dataflow-composed-task-runner/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/spring-cloud-dataflow-composed-task-runner/.github/workflows/stale.yml b/bitnami/spring-cloud-dataflow-composed-task-runner/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/spring-cloud-dataflow-composed-task-runner/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/spring-cloud-dataflow-composed-task-runner/CODE_OF_CONDUCT.md b/bitnami/spring-cloud-dataflow-composed-task-runner/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/spring-cloud-dataflow-composed-task-runner/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/spring-cloud-dataflow-composed-task-runner/CONTRIBUTING.md b/bitnami/spring-cloud-dataflow-composed-task-runner/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/spring-cloud-dataflow-composed-task-runner/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/spring-cloud-dataflow-composed-task-runner/LICENSE.md b/bitnami/spring-cloud-dataflow-composed-task-runner/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/spring-cloud-dataflow-composed-task-runner/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/spring-cloud-dataflow-shell/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/spring-cloud-dataflow-shell/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/spring-cloud-dataflow-shell/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/spring-cloud-dataflow-shell/.github/ISSUE_TEMPLATE/config.yml b/bitnami/spring-cloud-dataflow-shell/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/spring-cloud-dataflow-shell/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/spring-cloud-dataflow-shell/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/spring-cloud-dataflow-shell/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/spring-cloud-dataflow-shell/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/spring-cloud-dataflow-shell/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/spring-cloud-dataflow-shell/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/spring-cloud-dataflow-shell/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/spring-cloud-dataflow-shell/.github/workflows/stale.yml b/bitnami/spring-cloud-dataflow-shell/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/spring-cloud-dataflow-shell/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/spring-cloud-dataflow-shell/CODE_OF_CONDUCT.md b/bitnami/spring-cloud-dataflow-shell/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/spring-cloud-dataflow-shell/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/spring-cloud-dataflow-shell/CONTRIBUTING.md b/bitnami/spring-cloud-dataflow-shell/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/spring-cloud-dataflow-shell/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/spring-cloud-dataflow-shell/LICENSE.md b/bitnami/spring-cloud-dataflow-shell/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/spring-cloud-dataflow-shell/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/spring-cloud-dataflow/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/spring-cloud-dataflow/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/spring-cloud-dataflow/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/spring-cloud-dataflow/.github/ISSUE_TEMPLATE/config.yml b/bitnami/spring-cloud-dataflow/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/spring-cloud-dataflow/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/spring-cloud-dataflow/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/spring-cloud-dataflow/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/spring-cloud-dataflow/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/spring-cloud-dataflow/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/spring-cloud-dataflow/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/spring-cloud-dataflow/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/spring-cloud-dataflow/.github/workflows/stale.yml b/bitnami/spring-cloud-dataflow/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/spring-cloud-dataflow/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/spring-cloud-dataflow/CODE_OF_CONDUCT.md b/bitnami/spring-cloud-dataflow/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/spring-cloud-dataflow/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/spring-cloud-dataflow/CONTRIBUTING.md b/bitnami/spring-cloud-dataflow/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/spring-cloud-dataflow/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/spring-cloud-dataflow/LICENSE.md b/bitnami/spring-cloud-dataflow/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/spring-cloud-dataflow/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/spring-cloud-skipper-shell/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/spring-cloud-skipper-shell/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/spring-cloud-skipper-shell/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/spring-cloud-skipper-shell/.github/ISSUE_TEMPLATE/config.yml b/bitnami/spring-cloud-skipper-shell/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/spring-cloud-skipper-shell/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/spring-cloud-skipper-shell/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/spring-cloud-skipper-shell/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/spring-cloud-skipper-shell/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/spring-cloud-skipper-shell/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/spring-cloud-skipper-shell/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/spring-cloud-skipper-shell/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/spring-cloud-skipper-shell/.github/workflows/stale.yml b/bitnami/spring-cloud-skipper-shell/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/spring-cloud-skipper-shell/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/spring-cloud-skipper-shell/CODE_OF_CONDUCT.md b/bitnami/spring-cloud-skipper-shell/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/spring-cloud-skipper-shell/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/spring-cloud-skipper-shell/CONTRIBUTING.md b/bitnami/spring-cloud-skipper-shell/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/spring-cloud-skipper-shell/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/spring-cloud-skipper-shell/LICENSE.md b/bitnami/spring-cloud-skipper-shell/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/spring-cloud-skipper-shell/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/spring-cloud-skipper/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/spring-cloud-skipper/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/spring-cloud-skipper/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/spring-cloud-skipper/.github/ISSUE_TEMPLATE/config.yml b/bitnami/spring-cloud-skipper/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/spring-cloud-skipper/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/spring-cloud-skipper/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/spring-cloud-skipper/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/spring-cloud-skipper/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/spring-cloud-skipper/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/spring-cloud-skipper/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/spring-cloud-skipper/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/spring-cloud-skipper/.github/workflows/stale.yml b/bitnami/spring-cloud-skipper/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/spring-cloud-skipper/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/spring-cloud-skipper/CODE_OF_CONDUCT.md b/bitnami/spring-cloud-skipper/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/spring-cloud-skipper/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/spring-cloud-skipper/CONTRIBUTING.md b/bitnami/spring-cloud-skipper/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/spring-cloud-skipper/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/spring-cloud-skipper/LICENSE.md b/bitnami/spring-cloud-skipper/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/spring-cloud-skipper/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/suitecrm/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/suitecrm/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/suitecrm/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/suitecrm/.github/ISSUE_TEMPLATE/config.yml b/bitnami/suitecrm/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/suitecrm/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/suitecrm/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/suitecrm/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/suitecrm/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/suitecrm/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/suitecrm/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/suitecrm/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/suitecrm/.github/workflows/stale.yml b/bitnami/suitecrm/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/suitecrm/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/suitecrm/CODE_OF_CONDUCT.md b/bitnami/suitecrm/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/suitecrm/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/suitecrm/CONTRIBUTING.md b/bitnami/suitecrm/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/suitecrm/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/suitecrm/LICENSE.md b/bitnami/suitecrm/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/suitecrm/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/symfony/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/symfony/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/symfony/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/symfony/.github/ISSUE_TEMPLATE/config.yml b/bitnami/symfony/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/symfony/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/symfony/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/symfony/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/symfony/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/symfony/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/symfony/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/symfony/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/symfony/.github/workflows/stale.yml b/bitnami/symfony/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/symfony/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/symfony/CODE_OF_CONDUCT.md b/bitnami/symfony/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/symfony/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/symfony/CONTRIBUTING.md b/bitnami/symfony/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/symfony/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/symfony/LICENSE.md b/bitnami/symfony/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/symfony/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/telegraf/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/telegraf/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/telegraf/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/telegraf/.github/ISSUE_TEMPLATE/config.yml b/bitnami/telegraf/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/telegraf/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/telegraf/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/telegraf/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/telegraf/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/telegraf/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/telegraf/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/telegraf/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/telegraf/.github/workflows/stale.yml b/bitnami/telegraf/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/telegraf/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/telegraf/CODE_OF_CONDUCT.md b/bitnami/telegraf/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/telegraf/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/telegraf/CONTRIBUTING.md b/bitnami/telegraf/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/telegraf/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/telegraf/LICENSE.md b/bitnami/telegraf/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/telegraf/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/tensorflow-intel/.github/ISSUE_TEMPLATE.md b/bitnami/tensorflow-intel/.github/ISSUE_TEMPLATE.md deleted file mode 100644 index a7a1a6fc7a0f..000000000000 --- a/bitnami/tensorflow-intel/.github/ISSUE_TEMPLATE.md +++ /dev/null @@ -1,21 +0,0 @@ -**Description** - - - -**Steps to reproduce the issue:** - -1. [First Step] -2. [Second Step] -3. [and so on...] - -**Describe the results you received:** - - - -**Describe the results you expected:** - - - -**Additional information you deem important (e.g. issue happens only occasionally, environment details, etc.):** - - diff --git a/bitnami/tensorflow-intel/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/tensorflow-intel/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/tensorflow-intel/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/tensorflow-intel/.github/workflows/stale.yml b/bitnami/tensorflow-intel/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/tensorflow-intel/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/tensorflow-intel/CODE_OF_CONDUCT.md b/bitnami/tensorflow-intel/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/tensorflow-intel/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/tensorflow-intel/CONTRIBUTING.md b/bitnami/tensorflow-intel/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/tensorflow-intel/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/tensorflow-intel/LICENSE.md b/bitnami/tensorflow-intel/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/tensorflow-intel/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/tensorflow-resnet/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/tensorflow-resnet/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/tensorflow-resnet/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/tensorflow-resnet/.github/ISSUE_TEMPLATE/config.yml b/bitnami/tensorflow-resnet/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/tensorflow-resnet/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/tensorflow-resnet/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/tensorflow-resnet/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/tensorflow-resnet/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/tensorflow-resnet/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/tensorflow-resnet/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/tensorflow-resnet/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/tensorflow-resnet/.github/workflows/stale.yml b/bitnami/tensorflow-resnet/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/tensorflow-resnet/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/tensorflow-resnet/CODE_OF_CONDUCT.md b/bitnami/tensorflow-resnet/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/tensorflow-resnet/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/tensorflow-resnet/CONTRIBUTING.md b/bitnami/tensorflow-resnet/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/tensorflow-resnet/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/tensorflow-resnet/LICENSE.md b/bitnami/tensorflow-resnet/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/tensorflow-resnet/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/tensorflow-serving/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/tensorflow-serving/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/tensorflow-serving/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/tensorflow-serving/.github/ISSUE_TEMPLATE/config.yml b/bitnami/tensorflow-serving/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/tensorflow-serving/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/tensorflow-serving/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/tensorflow-serving/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/tensorflow-serving/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/tensorflow-serving/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/tensorflow-serving/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/tensorflow-serving/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/tensorflow-serving/.github/workflows/stale.yml b/bitnami/tensorflow-serving/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/tensorflow-serving/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/tensorflow-serving/CODE_OF_CONDUCT.md b/bitnami/tensorflow-serving/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/tensorflow-serving/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/tensorflow-serving/CONTRIBUTING.md b/bitnami/tensorflow-serving/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/tensorflow-serving/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/tensorflow-serving/LICENSE.md b/bitnami/tensorflow-serving/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/tensorflow-serving/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/testlink/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/testlink/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/testlink/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/testlink/.github/ISSUE_TEMPLATE/config.yml b/bitnami/testlink/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/testlink/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/testlink/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/testlink/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/testlink/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/testlink/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/testlink/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/testlink/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/testlink/.github/workflows/stale.yml b/bitnami/testlink/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/testlink/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/testlink/CODE_OF_CONDUCT.md b/bitnami/testlink/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/testlink/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/testlink/CONTRIBUTING.md b/bitnami/testlink/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/testlink/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/testlink/LICENSE.md b/bitnami/testlink/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/testlink/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/tests/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/tests/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/tests/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/tests/.github/ISSUE_TEMPLATE/config.yml b/bitnami/tests/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/tests/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/tests/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/tests/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/tests/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/tests/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/tests/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/tests/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/tests/.github/workflows/stale.yml b/bitnami/tests/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/tests/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/tests/CODE_OF_CONDUCT.md b/bitnami/tests/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/tests/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/tests/CONTRIBUTING.md b/bitnami/tests/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/tests/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/tests/LICENSE.md b/bitnami/tests/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/tests/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/thanos/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/thanos/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/thanos/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/thanos/.github/ISSUE_TEMPLATE/config.yml b/bitnami/thanos/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/thanos/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/thanos/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/thanos/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/thanos/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/thanos/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/thanos/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/thanos/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/thanos/.github/workflows/stale.yml b/bitnami/thanos/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/thanos/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/thanos/CODE_OF_CONDUCT.md b/bitnami/thanos/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/thanos/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/thanos/CONTRIBUTING.md b/bitnami/thanos/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/thanos/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/thanos/LICENSE.md b/bitnami/thanos/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/thanos/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/tomcat/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/tomcat/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/tomcat/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/tomcat/.github/ISSUE_TEMPLATE/config.yml b/bitnami/tomcat/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/tomcat/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/tomcat/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/tomcat/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/tomcat/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/tomcat/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/tomcat/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/tomcat/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/tomcat/.github/workflows/stale.yml b/bitnami/tomcat/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/tomcat/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/tomcat/CODE_OF_CONDUCT.md b/bitnami/tomcat/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/tomcat/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/tomcat/CONTRIBUTING.md b/bitnami/tomcat/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/tomcat/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/tomcat/LICENSE.md b/bitnami/tomcat/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/tomcat/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/trivy/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/trivy/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/trivy/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/trivy/.github/ISSUE_TEMPLATE/config.yml b/bitnami/trivy/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/trivy/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/trivy/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/trivy/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/trivy/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/trivy/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/trivy/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/trivy/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/trivy/.github/workflows/stale.yml b/bitnami/trivy/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/trivy/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/trivy/CODE_OF_CONDUCT.md b/bitnami/trivy/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/trivy/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/trivy/CONTRIBUTING.md b/bitnami/trivy/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/trivy/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/trivy/LICENSE.md b/bitnami/trivy/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/trivy/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/user-broker/.github/ISSUE_TEMPLATE.md b/bitnami/user-broker/.github/ISSUE_TEMPLATE.md deleted file mode 100644 index 91afdfd82d31..000000000000 --- a/bitnami/user-broker/.github/ISSUE_TEMPLATE.md +++ /dev/null @@ -1,22 +0,0 @@ -**Description** - - - -**Steps to reproduce the issue:** - -1. [First Step] -2. [Second Step] -3. [and so on...] - -**Describe the results you received:** - - - -**Describe the results you expected:** - - - -**Additional information you deem important (e.g. issue happens only occasionally, environment details, etc.):** - - - diff --git a/bitnami/user-broker/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/user-broker/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/user-broker/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/user-broker/.github/workflows/stale.yml b/bitnami/user-broker/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/user-broker/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/user-broker/CODE_OF_CONDUCT.md b/bitnami/user-broker/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/user-broker/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/user-broker/CONTRIBUTING.md b/bitnami/user-broker/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/user-broker/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/user-broker/LICENSE.md b/bitnami/user-broker/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/user-broker/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/wal-g/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/wal-g/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/wal-g/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/wal-g/.github/ISSUE_TEMPLATE/config.yml b/bitnami/wal-g/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/wal-g/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/wal-g/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/wal-g/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/wal-g/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/wal-g/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/wal-g/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/wal-g/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/wal-g/.github/workflows/stale.yml b/bitnami/wal-g/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/wal-g/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/wal-g/CODE_OF_CONDUCT.md b/bitnami/wal-g/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/wal-g/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/wal-g/CONTRIBUTING.md b/bitnami/wal-g/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/wal-g/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/wal-g/LICENSE.md b/bitnami/wal-g/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/wal-g/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/wavefront-adapter-for-istio/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/wavefront-adapter-for-istio/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/wavefront-adapter-for-istio/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/wavefront-adapter-for-istio/.github/ISSUE_TEMPLATE/config.yml b/bitnami/wavefront-adapter-for-istio/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/wavefront-adapter-for-istio/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/wavefront-adapter-for-istio/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/wavefront-adapter-for-istio/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/wavefront-adapter-for-istio/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/wavefront-adapter-for-istio/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/wavefront-adapter-for-istio/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/wavefront-adapter-for-istio/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/wavefront-adapter-for-istio/.github/workflows/stale.yml b/bitnami/wavefront-adapter-for-istio/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/wavefront-adapter-for-istio/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/wavefront-adapter-for-istio/CODE_OF_CONDUCT.md b/bitnami/wavefront-adapter-for-istio/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/wavefront-adapter-for-istio/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/wavefront-adapter-for-istio/CONTRIBUTING.md b/bitnami/wavefront-adapter-for-istio/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/wavefront-adapter-for-istio/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/wavefront-adapter-for-istio/LICENSE.md b/bitnami/wavefront-adapter-for-istio/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/wavefront-adapter-for-istio/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/wavefront-hpa-adapter/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/wavefront-hpa-adapter/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/wavefront-hpa-adapter/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/wavefront-hpa-adapter/.github/ISSUE_TEMPLATE/config.yml b/bitnami/wavefront-hpa-adapter/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/wavefront-hpa-adapter/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/wavefront-hpa-adapter/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/wavefront-hpa-adapter/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/wavefront-hpa-adapter/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/wavefront-hpa-adapter/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/wavefront-hpa-adapter/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/wavefront-hpa-adapter/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/wavefront-hpa-adapter/.github/workflows/stale.yml b/bitnami/wavefront-hpa-adapter/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/wavefront-hpa-adapter/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/wavefront-hpa-adapter/CODE_OF_CONDUCT.md b/bitnami/wavefront-hpa-adapter/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/wavefront-hpa-adapter/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/wavefront-hpa-adapter/CONTRIBUTING.md b/bitnami/wavefront-hpa-adapter/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/wavefront-hpa-adapter/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/wavefront-hpa-adapter/LICENSE.md b/bitnami/wavefront-hpa-adapter/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/wavefront-hpa-adapter/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/wavefront-kubernetes-collector/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/wavefront-kubernetes-collector/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/wavefront-kubernetes-collector/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/wavefront-kubernetes-collector/.github/ISSUE_TEMPLATE/config.yml b/bitnami/wavefront-kubernetes-collector/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/wavefront-kubernetes-collector/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/wavefront-kubernetes-collector/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/wavefront-kubernetes-collector/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/wavefront-kubernetes-collector/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/wavefront-kubernetes-collector/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/wavefront-kubernetes-collector/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/wavefront-kubernetes-collector/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/wavefront-kubernetes-collector/.github/workflows/stale.yml b/bitnami/wavefront-kubernetes-collector/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/wavefront-kubernetes-collector/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/wavefront-kubernetes-collector/CODE_OF_CONDUCT.md b/bitnami/wavefront-kubernetes-collector/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/wavefront-kubernetes-collector/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/wavefront-kubernetes-collector/CONTRIBUTING.md b/bitnami/wavefront-kubernetes-collector/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/wavefront-kubernetes-collector/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/wavefront-kubernetes-collector/LICENSE.md b/bitnami/wavefront-kubernetes-collector/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/wavefront-kubernetes-collector/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/wavefront-prometheus-storage-adapter/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/wavefront-prometheus-storage-adapter/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/wavefront-prometheus-storage-adapter/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/wavefront-prometheus-storage-adapter/.github/ISSUE_TEMPLATE/config.yml b/bitnami/wavefront-prometheus-storage-adapter/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/wavefront-prometheus-storage-adapter/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/wavefront-prometheus-storage-adapter/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/wavefront-prometheus-storage-adapter/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/wavefront-prometheus-storage-adapter/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/wavefront-prometheus-storage-adapter/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/wavefront-prometheus-storage-adapter/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/wavefront-prometheus-storage-adapter/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/wavefront-prometheus-storage-adapter/.github/workflows/stale.yml b/bitnami/wavefront-prometheus-storage-adapter/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/wavefront-prometheus-storage-adapter/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/wavefront-prometheus-storage-adapter/CODE_OF_CONDUCT.md b/bitnami/wavefront-prometheus-storage-adapter/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/wavefront-prometheus-storage-adapter/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/wavefront-prometheus-storage-adapter/CONTRIBUTING.md b/bitnami/wavefront-prometheus-storage-adapter/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/wavefront-prometheus-storage-adapter/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/wavefront-prometheus-storage-adapter/LICENSE.md b/bitnami/wavefront-prometheus-storage-adapter/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/wavefront-prometheus-storage-adapter/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/wavefront-proxy/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/wavefront-proxy/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/wavefront-proxy/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/wavefront-proxy/.github/ISSUE_TEMPLATE/config.yml b/bitnami/wavefront-proxy/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/wavefront-proxy/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/wavefront-proxy/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/wavefront-proxy/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/wavefront-proxy/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/wavefront-proxy/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/wavefront-proxy/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/wavefront-proxy/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/wavefront-proxy/.github/workflows/stale.yml b/bitnami/wavefront-proxy/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/wavefront-proxy/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/wavefront-proxy/CODE_OF_CONDUCT.md b/bitnami/wavefront-proxy/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/wavefront-proxy/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/wavefront-proxy/CONTRIBUTING.md b/bitnami/wavefront-proxy/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/wavefront-proxy/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/wavefront-proxy/LICENSE.md b/bitnami/wavefront-proxy/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/wavefront-proxy/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/wildfly/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/wildfly/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/wildfly/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/wildfly/.github/ISSUE_TEMPLATE/config.yml b/bitnami/wildfly/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/wildfly/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/wildfly/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/wildfly/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/wildfly/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/wildfly/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/wildfly/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/wildfly/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/wildfly/.github/workflows/stale.yml b/bitnami/wildfly/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/wildfly/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/wildfly/CODE_OF_CONDUCT.md b/bitnami/wildfly/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/wildfly/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/wildfly/CONTRIBUTING.md b/bitnami/wildfly/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/wildfly/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/wildfly/LICENSE.md b/bitnami/wildfly/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/wildfly/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/wordpress-intel/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/wordpress-intel/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/wordpress-intel/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/wordpress-intel/.github/ISSUE_TEMPLATE/config.yml b/bitnami/wordpress-intel/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/wordpress-intel/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/wordpress-intel/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/wordpress-intel/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/wordpress-intel/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/wordpress-intel/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/wordpress-intel/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/wordpress-intel/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/wordpress-intel/.github/workflows/stale.yml b/bitnami/wordpress-intel/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/wordpress-intel/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/wordpress-intel/CODE_OF_CONDUCT.md b/bitnami/wordpress-intel/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/wordpress-intel/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/wordpress-intel/CONTRIBUTING.md b/bitnami/wordpress-intel/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/wordpress-intel/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/wordpress-intel/LICENSE.md b/bitnami/wordpress-intel/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/wordpress-intel/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/wordpress-nginx/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/wordpress-nginx/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/wordpress-nginx/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/wordpress-nginx/.github/ISSUE_TEMPLATE/config.yml b/bitnami/wordpress-nginx/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/wordpress-nginx/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/wordpress-nginx/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/wordpress-nginx/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/wordpress-nginx/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/wordpress-nginx/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/wordpress-nginx/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/wordpress-nginx/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/wordpress-nginx/.github/workflows/stale.yml b/bitnami/wordpress-nginx/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/wordpress-nginx/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/wordpress-nginx/CODE_OF_CONDUCT.md b/bitnami/wordpress-nginx/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/wordpress-nginx/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/wordpress-nginx/CONTRIBUTING.md b/bitnami/wordpress-nginx/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/wordpress-nginx/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/wordpress-nginx/LICENSE.md b/bitnami/wordpress-nginx/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/wordpress-nginx/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/wordpress/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/wordpress/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/wordpress/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/wordpress/.github/ISSUE_TEMPLATE/config.yml b/bitnami/wordpress/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/wordpress/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/wordpress/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/wordpress/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/wordpress/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/wordpress/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/wordpress/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/wordpress/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/wordpress/.github/workflows/stale.yml b/bitnami/wordpress/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/wordpress/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/wordpress/CODE_OF_CONDUCT.md b/bitnami/wordpress/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/wordpress/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/wordpress/CONTRIBUTING.md b/bitnami/wordpress/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/wordpress/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/wordpress/LICENSE.md b/bitnami/wordpress/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/wordpress/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/bitnami/zookeeper/.github/ISSUE_TEMPLATE/bug_report.yml b/bitnami/zookeeper/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index 658fc40d2d6e..000000000000 --- a/bitnami/zookeeper/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,41 +0,0 @@ -name: 🐞 Bug -description: Create a report to help us improve -body: - - type: markdown - attributes: - value: | - Thank you for reporting an issue. Before you open the bug report please review the README file present in the root of this repository. - - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What steps will reproduce the bug? - description: Enter details about your bug. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - attributes: - label: What is the expected behavior? - description: If possible please provide textual output instead of screenshots. - - type: textarea - attributes: - label: What do you see instead? - description: If possible please provide textual output instead of screenshots. - validations: - required: true - - type: textarea - attributes: - label: Additional information - description: Tell us anything else you think we should know. diff --git a/bitnami/zookeeper/.github/ISSUE_TEMPLATE/config.yml b/bitnami/zookeeper/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0cec6c..000000000000 --- a/bitnami/zookeeper/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/bitnami/zookeeper/.github/ISSUE_TEMPLATE/feature_request.yml b/bitnami/zookeeper/.github/ISSUE_TEMPLATE/feature_request.yml deleted file mode 100644 index 7c812014aa08..000000000000 --- a/bitnami/zookeeper/.github/ISSUE_TEMPLATE/feature_request.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: "\U0001F680 Feature request" -description: Suggest an idea for this project -body: - - type: markdown - attributes: - value: | - Thank you for suggesting an idea to improve this Bitnami container image. - Please fill in as much of the following form as you're able. - - type: input - attributes: - label: Name and Version - description: Name and version of the affected container image - placeholder: bitnami/wordpress:1.2.3 - validations: - required: true - - type: textarea - attributes: - label: What is the problem this feature will solve? - validations: - required: true - - type: textarea - attributes: - label: What is the feature you are proposing to solve the problem? - description: Describe the requests. If you already have something in mind... PRs are welcome! - validations: - required: true - - type: textarea - attributes: - label: What alternatives have you considered? diff --git a/bitnami/zookeeper/.github/PULL_REQUEST_TEMPLATE.md b/bitnami/zookeeper/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index c2acbe6e0d70..000000000000 --- a/bitnami/zookeeper/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,32 +0,0 @@ - - -**Description of the change** - - - -**Benefits** - - - -**Possible drawbacks** - - - -**Applicable issues** - - - -**Additional information** - - diff --git a/bitnami/zookeeper/.github/workflows/stale.yml b/bitnami/zookeeper/.github/workflows/stale.yml deleted file mode 100644 index 0bf90080c817..000000000000 --- a/bitnami/zookeeper/.github/workflows/stale.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: '0 1 * * *' - -jobs: - stale: - runs-on: ubuntu-latest - steps: - - uses: actions/stale@v3 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - stale-issue-message: 'This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.' - stale-pr-message: 'This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.' - close-issue-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.' - close-pr-message: 'Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.' - days-before-stale: 15 - days-before-close: 5 - exempt-issue-labels: 'on-hold' - exempt-pr-labels: 'on-hold' diff --git a/bitnami/zookeeper/CODE_OF_CONDUCT.md b/bitnami/zookeeper/CODE_OF_CONDUCT.md deleted file mode 100644 index 48beb02e0808..000000000000 --- a/bitnami/zookeeper/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,17 +0,0 @@ -# Contributor Code of Conduct - -As contributors and maintainers of this project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities. - -Communication through any of Bitnami's channels (GitHub, mailing lists, Twitter, and so on) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. - -We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to this project to do the same. - -If any member of the community violates this code of conduct, the maintainers of this project may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate. - -If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us. - -If you have suggestions to improve this Code of Conduct, please submit an issue or PR. - -**Attribution** - -This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md diff --git a/bitnami/zookeeper/CONTRIBUTING.md b/bitnami/zookeeper/CONTRIBUTING.md deleted file mode 100644 index 4f5ce693ec65..000000000000 --- a/bitnami/zookeeper/CONTRIBUTING.md +++ /dev/null @@ -1,52 +0,0 @@ -# Contributing Guidelines - -Contributions are welcome via GitHub Pull Requests. This document outlines the process to help get your contribution accepted. - -Any type of contribution is welcome: new features, bug fixes, documentation improvements, etc. - -## How to Contribute - -1. Fork this repository, develop, and test your changes. -2. Submit a pull request. - -### Requirements - -When submitting a PR make sure that: -- It must pass CI jobs for linting and test the changes (if any). -- It must follow [container best practices](https://engineering.bitnami.com/articles/best-practices-writing-a-dockerfile.html). -- The title of the PR is clear enough. -- If necessary, add information to the repository's `README.md`. - -#### Sign Your Work - -The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, you only need to certify the guidelines from [developercertificate.org](https://developercertificate.org/). - -Then you just add a line to every git commit message: - - Signed-off-by: Joe Smith - -Use your real name (sorry, no pseudonyms or anonymous contributions.) - -If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. - -Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: - -``` -Author: Joe Smith -Date: Thu Feb 2 11:41:15 2018 -0800 - - Update README - - Signed-off-by: Joe Smith -``` - -Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. - -### PR Approval and Release Process - -1. Changes are manually reviewed by Bitnami team members usually within a business day. -2. Once the changes are accepted, the PR is tested (if needed) into the Bitnami CI pipeline, the container is deployed and tested (verification and functional tests) using docker-compose and Helm (if there is an associated Helm Chart). -3. The PR is merged by the reviewer(s) in the GitHub `master` branch. -4. Then our CI/CD system is going to push the container image to the different registries including the recently merged changes. - -***NOTE***: Please note that, in terms of time, may be a slight difference between the appearance of the code in GitHub and the image with the changes in the different registries. diff --git a/bitnami/zookeeper/LICENSE.md b/bitnami/zookeeper/LICENSE.md deleted file mode 100644 index cdc8ab40132d..000000000000 --- a/bitnami/zookeeper/LICENSE.md +++ /dev/null @@ -1,13 +0,0 @@ -Copyright © 2022 Bitnami - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. diff --git a/scripts/fetch-commits.sh b/scripts/fetch-commits.sh new file mode 100644 index 000000000000..bc1ec957e85e --- /dev/null +++ b/scripts/fetch-commits.sh @@ -0,0 +1,118 @@ +#!/bin/bash + +set -o errexit +set -o nounset +set -o pipefail +set -o xtrace # Uncomment this line for debugging purpose + +TARGET_DIR="." + +COMMIT_SHIFT="${1:-0}" # Used when you push commits manually + +function queryRepos() { + local page=0 + local repos="[]" # Initial empty JSON array + local -r repos_per_page="100" + + while [[ "$page" -gt -1 ]]; do + # Query only the public repos since we won't add private containers to bitnami/containers + page_repos="$(curl -H 'Content-Type: application/json' -H 'Accept: application/json' "https://api.github.com/orgs/bitnami/repos?type=public&per_page=${repos_per_page}&page=${page}")" + repos="$(jq -s 'reduce .[] as $x ([]; . + $x)' <(echo "$repos") <(echo "$page_repos"))" + n_repos="$(jq length <<< "$page_repos")" + if [[ "$n_repos" -lt "$repos_per_page" ]]; then + page="-1" + else + page="$((page + 1))" + fi + done + + echo "$repos" +} + +function getContainerRepos() { + local -r repos="$(queryRepos)" + local -r container_repos="$(jq -r '[ .[] | select(.name | test("bitnami-docker-.")) ]' <<< "$repos")" + echo "$container_repos" > /tmp/repos + echo "$container_repos" +} + +# Commits a directory +function commitChanges() { + git config user.name "Bitnami Containers" + git config user.email "containers@bitnami.com" + + # git diff --exit-code --quiet + git diff --exit-code || (git add -A && git commit -m "Sync ${name} files") +} + +function pushChanges() { + git config user.name "Bitnami Containers" + git config user.email "containers@bitnami.com" + git push +} + +function findCommitsToSync() { + local origin_name="${1:?Missing origin name}" + # Get all commits IDs on the origin + local -r commits=($(git rev-list "${origin_name}/master" -- .)) + # Find the commit that doesn't have changes respect the container folder + # Get the last commit message in the container folder + local shift=$((COMMIT_SHIFT + 1)) + local -r last_commit_message="$(git log -n "$shift" --pretty=tformat:"%s" containers/"$origin_name" | tail -n 1)" + # Search on the container origin repo the ID for the latest commit we have locally in the container folder + local -r last_synced_commit_id="$(git rev-list "$origin_name"/master --grep="${last_commit_message}")" + local commits_to_sync="" + local max=20 # If we need to sync more than 20 commits there must be something wrong since we run the job on a daily basis + for commit in "${commits[@]}"; do + if [[ "$commit" != "$last_synced_commit_id" ]] && [[ "$max" -gt "0" ]]; then + commits_to_sync="${commit} ${commits_to_sync}" + else + # We reached the last commit synced + break + fi + max=$((max - 1)) + done + + [[ "$max" -eq "0" ]] && echo "Last commit not found into the original repo history" && exit 1 + printf "$commits_to_sync" +} + +syncCommit() { + local -r commit_id="${1:?Missing commit id}" + local -r app="${2:?Missing app name}" + local -r patch_file="$(git format-patch -1 "$commit_id")" + # Apply patch + git am --directory "containers/${app}" "$patch_file" + rm -f "$patch_file" +} + +function syncRepos() { + local -r repos="$(getContainerRepos)" + + mkdir -p "$TARGET_DIR" + + # Build array of app names since we need to exclude them when moving files + local apps=("mock") + local -r urls=($(echo "$repos" | jq -r '.[].html_url')) + for repo_url in "${urls[@]}"; do + name="${repo_url:42}" # 42 is the length of https://github.com/bitnami/bitnami-docker- + apps=("${apps[@]}" "$name") + done + echo "$repos" | jq -r '.[].html_url' | while read -r repo_url; do + name="${repo_url:42}" # 42 is the length of https://github.com/bitnami/bitnami-docker- + ( + cd "$TARGET_DIR" + # Fetch the old repo master + git remote add --fetch "$name" "$repo_url" + read -r -a commits_to_sync <<< "$(findCommitsToSync "$name")" + for commit in "${commits_to_sync[@]}"; do + syncCommit "$commit" "$name" + done + git remote remove "$name" + ) + done + + pushChanges +} + +syncRepos diff --git a/scripts/sync-repos.sh b/scripts/sync-repos.sh index 8a7fa7af26d9..bef3fae828af 100644 --- a/scripts/sync-repos.sh +++ b/scripts/sync-repos.sh @@ -7,29 +7,6 @@ set -o xtrace # Uncomment this line for debugging purpose TARGET_DIR="." -# App and repo that will be used as base -BASE_REPO="https://github.com/bitnami/bitnami-docker-wordpress" - -function joinStrings() { - local a=("${@:3}") - printf "%s" "$2${a[@]/#/$1}" -} - -function moveFilesExcluding() { - local -r dest="${1:?Missing destination directory}" - shift - local -r excludeFiles=("$@") -echo "Files to exclude: ${excludeFiles[@]}" - mkdir -p "$dest" - - local -r f_exclude_flags=($(joinStrings ' -and ! -name ' "${excludeFiles[@]}")) -echo "${f_exclude_flags[@]}" - find . -depth 1 ! -name "${f_exclude_flags[@]}" | while read -r file; do - cp -a "$file" "${dest}/" - rm -Rf "$file" - done -} - function queryRepos() { local page=0 local repos="[]" # Initial empty JSON array @@ -57,18 +34,10 @@ function getContainerRepos() { echo "$container_repos" } -# Commits a directory -function commitChanges() { - git config user.name "Bitnami Containers" - git config user.email "containers@bitnami.com" - - git diff --exit-code || (git add -A && git commit -m "Sync ${name} files") -} - function pushChanges() { git config user.name "Bitnami Containers" git config user.email "containers@bitnami.com" - git push + git push origin main } function mergeRepos() { @@ -92,8 +61,7 @@ function mergeRepos() { ( cd "$TARGET_DIR" mkdir -p "containers/${name}" # Create directory for the app - # Back up the README.md to avoid getting merge conflicts - #mv README.md README.md.back + # clone the repositoy outside of this one git clone "$repo_url" ../temporal/"$name" ( @@ -103,16 +71,9 @@ function mergeRepos() { ) # Fetch the old repo and merge maintaining history git remote add --fetch "$name" "../temporal/${name}" - git merge "${name}/master" --allow-unrelated-histories --no-log --no-ff -Xtheirs #--no-commit - #git checkout main "${special_files[@]}" + git merge "${name}/master" --allow-unrelated-histories --no-log --no-ff -Xtheirs git remote remove "$name" rm -Rf ../temporal/"$name" - # Move the content to the app directory - # moveFilesExcluding "containers/${name}" "${static_files[@]}" "README.md.back" "${special_files[@]}" "${apps[@]}" - # Recover README.md - #mv README.md.back README.md - #commitChanges -exit 0 ) done