pre-commit

Author: jaimergp

blog/2020-02-04-GSoC.md

@@ -25,7 +25,7 @@ and user interactions on GitHub.
 
 Want to be a part of the team? Great! Take a look at the projects below
 and get in touch with us on GitHub! You can check the [GSoC
-label](<https://github.com/regro/cf-scripts/labels/GSOC>) for a
+label](https://github.com/regro/cf-scripts/labels/GSOC) for a
 detailed listing of the issues that need work.
 
 1.  Maintenance and Refactoring
@@ -34,24 +34,24 @@ detailed listing of the issues that need work.
     are great for people with a range of experience from beginners to
     true code ninjas.
 
-    -   Integration Testing for the Autotick Bot
+    - Integration Testing for the Autotick Bot
 
-        > Run true integration testing on a copy of the graph to better
-        > test code changes and improve our CI process.
-        >
-        > **Issue**: <https://github.com/regro/cf-scripts/issues/261>
-        >
-        > **Experience Level**: advanced
+      > Run true integration testing on a copy of the graph to better
+      > test code changes and improve our CI process.
+      >
+      > **Issue**: <https://github.com/regro/cf-scripts/issues/261>
+      >
+      > **Experience Level**: advanced
 
-    -   Work on the "code hardening"
-        [Milestone](<https://github.com/regro/cf-scripts/milestone/4>)
+    - Work on the "code hardening"
+      [Milestone](https://github.com/regro/cf-scripts/milestone/4)
 
-        Address any of the issues in the milestone above related to code
-        refactoring and cleanup.
+      Address any of the issues in the milestone above related to code
+      refactoring and cleanup.
 
-        **Issues**: <https://github.com/regro/cf-scripts/milestone/4>
+      **Issues**: <https://github.com/regro/cf-scripts/milestone/4>
 
-        **Experience Level**: beginner to advanced
+      **Experience Level**: beginner to advanced
 
 2.  Automated PRs for Globally Pinned Packages
 

blog/2020-03-05-grayskull.md

@@ -261,16 +261,16 @@ extra:
 
 ### Major differences
 
-| Attribute | Grayskull (0.2.1) | Skeleton (3.18.11) |
-| --------- | ----------------- | ------------------ |
-  **Command**             | ✅ grayskull pypi pytest                                                                                       | ✅ conda skeleton pypi pytest |
-  **Time**                | ✅ 4 seconds                                                                                                   | ❌ 31 seconds |
-  **License**             | ✅ Added the license file and license type correctly                                                           | ❗️ Added just the license type |
-  **Host Requirements**   | ✅ Added correctly all the host requirements                                                                   | ❌ it didn't add the correctly the host dependencies. It added unnecessary dependencies and it is missing quite a few of them necessary to build the package |
-  **Run Requirements**    | ✅ Missing just setuptools from the host requirements (but this dependency is not defined on pytest package)   | ❌ incorrect dependencies added to the project |
-  **Selectors**           | ✅ Skipping correctly Python 2 and added selectors for windows and python versions                             | ❌ it didn't add any information regarding selectors. Actually conda-build added wrong information which will result in a broken recipe. For example 'sys_platform == win32' was added which is a wrong format for conda recipes |
-  **Entry points**        | ✅ Added all entry points correctly                                                                            | ❌ No entry points |
-  **Does it build?**      | ✅ YES                                                                                                         | ❌ NO |
+| Attribute             | Grayskull (0.2.1)                                                                                            | Skeleton (3.18.11)                                                                                                                                                                                                               |
+| --------------------- | ------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **Command**           | ✅ grayskull pypi pytest                                                                                     | ✅ conda skeleton pypi pytest                                                                                                                                                                                                    |
+| **Time**              | ✅ 4 seconds                                                                                                 | ❌ 31 seconds                                                                                                                                                                                                                    |
+| **License**           | ✅ Added the license file and license type correctly                                                         | ❗️ Added just the license type                                                                                                                                                                                                  |
+| **Host Requirements** | ✅ Added correctly all the host requirements                                                                 | ❌ it didn't add the correctly the host dependencies. It added unnecessary dependencies and it is missing quite a few of them necessary to build the package                                                                     |
+| **Run Requirements**  | ✅ Missing just setuptools from the host requirements (but this dependency is not defined on pytest package) | ❌ incorrect dependencies added to the project                                                                                                                                                                                   |
+| **Selectors**         | ✅ Skipping correctly Python 2 and added selectors for windows and python versions                           | ❌ it didn't add any information regarding selectors. Actually conda-build added wrong information which will result in a broken recipe. For example 'sys_platform == win32' was added which is a wrong format for conda recipes |
+| **Entry points**      | ✅ Added all entry points correctly                                                                          | ❌ No entry points                                                                                                                                                                                                               |
+| **Does it build?**    | ✅ YES                                                                                                       | ❌ NO                                                                                                                                                                                                                            |
 
 In the case of `noarch: python`, Grayskull is smart enough to detect
 when the recipe supports it, which is not done by Skeleton. It is
@@ -348,11 +348,11 @@ grayskul pypi pytest requests=2.21.0 colorama
 
 ## Future plans
 
-> -   For the next major version (1.0.0) it is planned to add the
->     functionality to be able to load the recipe and update just parts
->     of it;
-> -   Generate Conda recipes using CRAN (R) channel (2.0.0);
-> -   Generate Conda recipes using Conan (C++) channel (3.0.0);
+> - For the next major version (1.0.0) it is planned to add the
+>   functionality to be able to load the recipe and update just parts
+>   of it;
+> - Generate Conda recipes using CRAN (R) channel (2.0.0);
+> - Generate Conda recipes using Conan (C++) channel (3.0.0);
 
 ## Issues
 
@@ -361,7 +361,7 @@ the repository: <https://github.com/marcelotrevisani/grayskull/issues>.
 
 Contributions are very welcome! :)
 
-------------------------------------------------------------------------
+---
 
 This work was possible thanks to the [NumFOCUS](https://numfocus.org/)
 Small Development Grant program.

blog/2020-03-10-pypy.md

@@ -11,10 +11,10 @@ environment
 
 Supported platforms are,
 
-> -   Linux-x86_64 (glibc 2.12 or newer)
-> -   OSX-x86_64 (OSX 10.9 or newer)
-> -   Linux-aarch64 (glibc 2.17 or newer)
-> -   Linux-ppc64le (glibc 2.17 or newer)
+> - Linux-x86_64 (glibc 2.12 or newer)
+> - OSX-x86_64 (OSX 10.9 or newer)
+> - Linux-aarch64 (glibc 2.17 or newer)
+> - Linux-ppc64le (glibc 2.17 or newer)
 
 <!--truncate-->
 
@@ -74,41 +74,41 @@ a dependency on python_abi. For eg,
 ```yaml
 requirements:
   host:
-   - python 3.6
+    - python 3.6
   run:
-   - python
+    - python
 ```
 
 is rendered as,
 
 ```yaml
 requirements:
   host:
-   - python 3.6.10 h9d8adfe_1009_cpython
+    - python 3.6.10 h9d8adfe_1009_cpython
   run:
-   - python >=3.6,<3.7.0a0
-   - python_abi 3.6 *_cp36m
+    - python >=3.6,<3.7.0a0
+    - python_abi 3.6 *_cp36m
 ```
 
 whereas,
 
 ```yaml
 requirements:
   host:
-   - python 3.6 *_73_pypy
+    - python 3.6 *_73_pypy
   run:
-   - python
+    - python
 ```
 
 is rendered as,
 
 ```yaml
 requirements:
   host:
-   - python 3.6.9 0_73_pypy
+    - python 3.6.9 0_73_pypy
   run:
-   - python >=3.6,<3.7.0a0
-   - python_abi 3.6 *_pypy36_pp73
+    - python >=3.6,<3.7.0a0
+    - python_abi 3.6 *_pypy36_pp73
 ```
 
 Note that the PyPy ABI tag has `pp73` at the end which

blog/2020-07-06-scipy-bof.md

@@ -20,23 +20,23 @@ seeking new viewpoints and opinions!
 
 ### State of Packaging
 
--   What is the state of conda-forge today?
--   What improvements are in the works?
+- What is the state of conda-forge today?
+- What improvements are in the works?
 
 ### New features/ideas
 
--   What is something that's not in the works that you'd like to see
-    updated/improved?
--   What are ways that folks who are interested but new to the community
-    can get involved?
+- What is something that's not in the works that you'd like to see
+  updated/improved?
+- What are ways that folks who are interested but new to the community
+  can get involved?
 
 ### Maintenance
 
--   What is the maintenance burden and what pain points does it create?
--   What are strategies to mitigate this burden?
+- What is the maintenance burden and what pain points does it create?
+- What are strategies to mitigate this burden?
 
 ### Questions to the audience
 
--   What are your pain points when engaging with conda forge?
--   What is something new you'd like to see happen?
--   What feedback do audience members have?
+- What are your pain points when engaging with conda forge?
+- What is something new you'd like to see happen?
+- What feedback do audience members have?

blog/2020-10-29-macos-arm64.md

@@ -131,7 +131,7 @@ conda smithy rerender
 ```
 
 For python packages, add one or more of the following to
-`recipe/meta.yaml` as needed, noting that you *must* only add
+`recipe/meta.yaml` as needed, noting that you _must_ only add
 `numpy`, `cython`, and/or `pybind11`
 if they are used in `host:` as well,
 

blog/2020-12-26-year-in-review.md

@@ -14,53 +14,53 @@ the big accomplishments our community has made this year.
 The `conda-forge` community has grown immensely this year. Here are some
 numbers to help give you an idea of the scale of our growth.
 
--   The community has added 3,751 new, unique `conda` packages this
-    year, along with a corresponding number of new feedstocks.
--   For the majority of 2020, the `conda-forge` channel on
-    `anaconda.org` exceeded 100 million downloads per month.
--   In July of 2020, the `conda-forge` channel passed 2 billion total,
-    all-time downloads.
--   We've grown our core developer community, adding seven new members
-    to the `conda-forge` Core team and at least two members to the
-    `staged-recipes` team.
--   We now have over 2,500 recipe maintainers in the `conda-forge`
-    GitHub organization.
+- The community has added 3,751 new, unique `conda` packages this
+  year, along with a corresponding number of new feedstocks.
+- For the majority of 2020, the `conda-forge` channel on
+  `anaconda.org` exceeded 100 million downloads per month.
+- In July of 2020, the `conda-forge` channel passed 2 billion total,
+  all-time downloads.
+- We've grown our core developer community, adding seven new members
+  to the `conda-forge` Core team and at least two members to the
+  `staged-recipes` team.
+- We now have over 2,500 recipe maintainers in the `conda-forge`
+  GitHub organization.
 
 ## Big New Features
 
 We've also shipped a ton of big updates to our core infrastructure this
 year. These updates include
 
--   `PyPy` **support**: We added support for `PyPy` 3.6 and now supply
-    one of the biggest stacks of `PyPy`-enabled packages in the `PyPy`
-    ecosystem.
--   **automerge**: We now support the automatic merging of PRs on
-    feedstocks using the `automerge` label or through an opt-in setting
-    in the `conda-forge.yml`.
--   `R` **4.0 migration**: This migration was the first one to use our
-    `automerge` infrastructure at scale. With it, we completed a
-    complete rebuild/upgrade of the `R` ecosystem in about a week.
--   `Python` **updates**: We deprecated `Python` 2.7, completed the
-    `Python` 3.8 migration, and got about 75% of the way through the
-    `Python` 3.9 migration.
--   **compiler upgrades**: We upgraded our compiler infrastructure to
-    `GCC` 9 and `clang` 11.
--   **CentOS 7 and CentOS 6 EOL**: We shipped an option to enable our
-    compilers to use the CentOS 7 `sysroot` in preparation for the
-    CentOS 6 EOL. We hope to complete the move to CentOS 7 early next
-    year.
--   **miniforge**: We built our own standalone, `miniconda`-like
-    installers. These support a broad range of platforms, including
-    `osx-arm64` and `linux-aarch64`.
--   **standalone Windows stack**: We fully decoupled our Windows recipes
-    from the `defaults` channel by rebuilding the `msys2` recipes.
--   **Apple silicon support**: We added support for Apple silicon with
-    our `osx-arm64` platform. This platform is our first one to use a
-    fully cross-compiled infrastructure.
--   **CUDA support**: We added support for building CUDA packages on
-    windows and added CUDA 11.0 support.
+- `PyPy` **support**: We added support for `PyPy` 3.6 and now supply
+  one of the biggest stacks of `PyPy`-enabled packages in the `PyPy`
+  ecosystem.
+- **automerge**: We now support the automatic merging of PRs on
+  feedstocks using the `automerge` label or through an opt-in setting
+  in the `conda-forge.yml`.
+- `R` **4.0 migration**: This migration was the first one to use our
+  `automerge` infrastructure at scale. With it, we completed a
+  complete rebuild/upgrade of the `R` ecosystem in about a week.
+- `Python` **updates**: We deprecated `Python` 2.7, completed the
+  `Python` 3.8 migration, and got about 75% of the way through the
+  `Python` 3.9 migration.
+- **compiler upgrades**: We upgraded our compiler infrastructure to
+  `GCC` 9 and `clang` 11.
+- **CentOS 7 and CentOS 6 EOL**: We shipped an option to enable our
+  compilers to use the CentOS 7 `sysroot` in preparation for the
+  CentOS 6 EOL. We hope to complete the move to CentOS 7 early next
+  year.
+- **miniforge**: We built our own standalone, `miniconda`-like
+  installers. These support a broad range of platforms, including
+  `osx-arm64` and `linux-aarch64`.
+- **standalone Windows stack**: We fully decoupled our Windows recipes
+  from the `defaults` channel by rebuilding the `msys2` recipes.
+- **Apple silicon support**: We added support for Apple silicon with
+  our `osx-arm64` platform. This platform is our first one to use a
+  fully cross-compiled infrastructure.
+- **CUDA support**: We added support for building CUDA packages on
+  windows and added CUDA 11.0 support.
 
-------------------------------------------------------------------------
+---
 
 We know that this year has been extremely difficult for so many of our
 community members and that the fantastic success of `conda-forge` would