ci: conda: Move conda stuff to .conda directory to unify with OOT style.

conda_recipe has been lonely ever since everything else in .packaging
was removed, and this gives a uniform style between the main tree and
OOT modules.

Signed-off-by: Ryan Volz <ryan.volz@gmail.com>
(cherry picked from commit 7ed741eb8add69ca896abc0cc575c07e827733f6)
Signed-off-by: Jeff Long <willcode4@gmail.com>

9 files changed, 63 insertions, 22 deletions

diff --git a/.conda/README b/.conda/README
new file mode 100644
index 000000000..041f1a4aa
--- /dev/null
+++ b/.conda/README
@@ -0,0 +1,30 @@
+Users
+*****
+
+This recipe is primarily used for CI builds, although it is possible to use it
+locally from a checked-out git repository with "conda-build".
+
+Developers
+**********
+
+CI builds use this recipe and the settings in .conda/conda-forge.yml. Any changes
+to the recipe should be accompanied by running
+
+    conda-smithy rerender --feedstock_config .conda/conda-forge.yml -c auto
+    git rm -f .github/workflows/automerge.yml .github/workflows/webservices.yml .circleci/config.yml
+    git commit --amend -s
+
+so that the generated build scripts are updated when necessary.
+***** RUN THE ABOVE TO CHECK FOR UPDATES WHENEVER EDITS ARE MADE in .conda *****
+
+You can also re-render from a pull request by starting a comment with "/rerender", which will trigger a Github workflow to perform the above steps.
+
+The CI will build conda packages for commits and pull requests, and it will
+upload the packages to Anaconda Cloud on commits to the branch specified
+in the configuration below. The channel and label that the packages are
+uploaded to are set in the recipe directory in conda_build_config.yaml.
+Uploads to Anaconda Cloud also require an API token to be set to the
+BINSTAR_TOKEN environment variable. Documentation for token generation:
+https://docs.anaconda.com/anacondaorg/user-guide/tasks/work-with-accounts/#creating-access-tokens
+To populate BINSTAR_TOKEN for CI jobs, add the token as a secret, e.g.:
+https://docs.github.com/en/actions/reference/encrypted-secrets
diff --git a/.conda/conda-forge.yml b/.conda/conda-forge.yml
new file mode 100644
index 000000000..3ce96c201
--- /dev/null
+++ b/.conda/conda-forge.yml
@@ -0,0 +1,32 @@
+# This file defines the configuration for building conda packages with CI.
+# The actual files for running the CI are created/updated by "conda-smithy".
+# You should edit only this file and the recipe files (in recipe_dir, below)
+# and not any of the automatically-generated files in e.g. .ci_support,
+# .scripts, or .github/workflows/conda-build.yml.
+
+# See https://conda-forge.org/docs/maintainer/conda_forge_yml.html for
+# documentation on possible keys and values.
+
+clone_depth: 0
+github_actions:
+  cancel_in_progress: false
+  store_build_artifacts: true
+os_version:
+  linux_64: cos7
+provider:
+  linux: github_actions
+  osx: github_actions
+  win: github_actions
+recipe_dir: .conda/recipe
+# skip unnecessary files since this is not a full-fledged conda-forge feedstock
+skip_render:
+  - README.md
+  - LICENSE.txt
+  - .gitattributes
+  - .gitignore
+  - build-locally.py
+  - LICENSE
+test: native_and_emulated
+# enable uploads to Anaconda Cloud from specified branches only
+# ***** UPDATE THIS FOR MAINTENANCE BRANCHES ********************************
+upload_on_branch: main
diff --git a/.packaging/conda_recipe/bld.bat b/.conda/recipe/bld.bat
index b02bbe89e..b02bbe89e 100644
--- a/.packaging/conda_recipe/bld.bat
+++ b/.conda/recipe/bld.bat
diff --git a/.packaging/conda_recipe/build.sh b/.conda/recipe/build.sh
index c93c35cc4..c93c35cc4 100644
--- a/.packaging/conda_recipe/build.sh
+++ b/.conda/recipe/build.sh
diff --git a/.packaging/conda_recipe/conda_build_config.yaml b/.conda/recipe/conda_build_config.yaml
index 008614d1a..008614d1a 100644
--- a/.packaging/conda_recipe/conda_build_config.yaml
+++ b/.conda/recipe/conda_build_config.yaml
diff --git a/.packaging/conda_recipe/meta.yaml b/.conda/recipe/meta.yaml
index f97e40c5c..f97e40c5c 100644
--- a/.packaging/conda_recipe/meta.yaml
+++ b/.conda/recipe/meta.yaml
diff --git a/.packaging/conda_recipe/yum_requirements.txt b/.conda/recipe/yum_requirements.txt
index d72433568..d72433568 100644
--- a/.packaging/conda_recipe/yum_requirements.txt
+++ b/.conda/recipe/yum_requirements.txt
diff --git a/.github/workflows/conda-rerender-ci.yml b/.github/workflows/conda-rerender-ci.yml
index 051309db8..d38c334d3 100644
--- a/.github/workflows/conda-rerender-ci.yml
+++ b/.github/workflows/conda-rerender-ci.yml
@@ -48,7 +48,7 @@ jobs:
       - name: Re-render
         shell: bash -l {0}
         run: |
-          conda smithy rerender --feedstock_config .conda-forge.yml
+          conda smithy rerender --feedstock_config .conda/conda-forge.yml
       - name: Commit and push
         uses: EndBug/add-and-commit@v7
         with:
diff --git a/.packaging/conda_recipe/README b/.packaging/conda_recipe/README
deleted file mode 100644
index a23c4e562..000000000
--- a/.packaging/conda_recipe/README
+++ /dev/null
@@ -1,21 +0,0 @@
-Users
-*****
-
-This recipe is primarily used for CI builds, although it is possible to use it
-locally from a checked-out git repository with "conda-build".
-
-Developers
-**********
-
-CI builds use this recipe and the settings in ../../.conda-forge.yml. Any changes
-to the recipe should be accompanied by running
-
-    conda-smithy rerender --feedstock_config .conda-forge.yml -c auto
-    git rm -f .github/workflows/automerge.yml .github/workflows/webservices.yml .circleci/config.yml
-    git commit --amend -s
-
-so that the generated build scripts are updated when necessary.
-
-You can also re-render from a pull request by starting a comment with "/rerender", which will trigger a Github workflow to perform the above steps.
-
-Consult the .conda-forge.yml file for additional documentation.