Hi! This is the friendly conda-forge-admin automated user.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/bad_recipe) and found some lint.

Here's what I've got...

For recipes/bad_recipe:

• The home item is expected in the about section.
• The license item is expected in the about section.
• The summary item is expected in the about section.
• The recipe could do with some maintainers listed in the "extra/recipe-maintainers" section.
• The recipe must have some tests.

This is so awesome, @pelson. Thanks for getting this to work.

Hi! This is the friendly conda-forge-admin automated user.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/bad_recipe) and found some lint.

Here's what I've got...

For recipes/bad_recipe:

• The home item is expected in the about section.
• The license item is expected in the about section.
• The summary item is expected in the about section.
• The recipe could do with some maintainers listed in the "extra/recipe-maintainers" section.
• The recipe must have some tests.

Hi! This is the friendly conda-forge-admin automated user.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/bad_recipe) and found some lint.

Here's what I've got...

For recipes/bad_recipe:

• The home item is expected in the about section.
• The license item is expected in the about section.
• The summary item is expected in the about section.
• The recipe could do with some maintainers listed in the "extra/recipe-maintainers" section.
• The recipe must have some tests.
• The recipe must have a build/number section.

Hi! This is the friendly conda-forge-admin automated user.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/bad_recipe) and found some lint.

Here's what I've got...

For recipes/bad_recipe:

• The home item is expected in the about section.
• The license item is expected in the about section.
• The summary item is expected in the about section.
• The recipe could do with some maintainers listed in the "extra/recipe-maintainers" section.
• The recipe must have some tests.
• The recipe must have a build/number section.
• The requirements/build section should be defined before the requirements/run section.

Hi! This is the friendly conda-forge-admin automated user.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/bad_recipe) and found some lint.

Here's what I've got...

For recipes/bad_recipe:

• The home item is expected in the about section.
• The license item is expected in the about section.
• The summary item is expected in the about section.
• The recipe could do with some maintainers listed in the "extra/recipe-maintainers" section.
• The recipe must have some tests.
• The recipe must have a build/number section.

Hi! This is the friendly conda-forge-admin automated user.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/bad_recipe) and found some lint.

Here's what I've got...

For recipes/bad_recipe:

• The home item is expected in the about section.
• The license item is expected in the about section.
• The summary item is expected in the about section.
• The recipe could do with some maintainers listed in the "extra/recipe-maintainers" section.
• The recipe must have some tests.
• The recipe must have a build/number section.
• The requirements/build section should be defined before the requirements/run section.

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/bad_recipe) and found some lint.

Here's what I've got...

For recipes/bad_recipe:

• The home item is expected in the about section.
• The license item is expected in the about section.
• The summary item is expected in the about section.
• The recipe could do with some maintainers listed in the "extra/recipe-maintainers" section.
• The recipe must have some tests.

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/bad_recipe) and found some lint.

Here's what I've got...

For recipes/bad_recipe:

• The home item is expected in the about section.
• The license item is expected in the about section.
• The summary item is expected in the about section.
• The recipe could do with some maintainers listed in the "extra/recipe-maintainers" section.
• The recipe must have some tests.
• The recipe must have a build/number section.
• The requirements/build section should be defined before the requirements/run section.

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/bad_recipe) and found some lint.

Here's what I've got...

For recipes/bad_recipe:

• The home item is expected in the about section.
• The license item is expected in the about section.
• The summary item is expected in the about section.
• The recipe could do with some maintainers listed in the "extra/recipe-maintainers" section.
• The recipe must have some tests.
• The recipe must have a build/number section.

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/bad_recipe) and found some lint.

Here's what I've got...

For recipes/bad_recipe:

• The home item is expected in the about section.
• The license item is expected in the about section.
• The summary item is expected in the about section.
• The recipe could do with some maintainers listed in the "extra/recipe-maintainers" section.
• The recipe must have some tests.
• The recipe must have a build/number section.
• The requirements/build section should be defined before the requirements/run section.

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/bad_recipe) and found some lint.

Here's what I've got...

For recipes/bad_recipe:

• The home item is expected in the about section.
• The license item is expected in the about section.
• The summary item is expected in the about section.
• The recipe could do with some maintainers listed in the "extra/recipe-maintainers" section.
• The recipe must have some tests.
• The recipe must have a build/number section.

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/bad_recipe) and found some lint.

Here's what I've got...

For recipes/bad_recipe:

• The home item is expected in the about section.
• The license item is expected in the about section.
• The summary item is expected in the about section.
• The recipe could do with some maintainers listed in the extra/recipe-maintainers section.
• The recipe must have some tests.
• The recipe must have a build/number section.

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/bad_recipe) and found some lint.

Here's what I've got...

For recipes/bad_recipe:

• The home item is expected in the about section.
• The license item is expected in the about section.
• The summary item is expected in the about section.
• The recipe could do with some maintainers listed in the extra/recipe-maintainers section.
• The recipe must have some tests.
• The recipe must have a build/number section.
• There should be one empty line at the end of the file.

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/bad_recipe) and found some lint.

Here's what I've got...

For recipes/bad_recipe:

• The home item is expected in the about section.
• The license item is expected in the about section.
• The summary item is expected in the about section.
• The recipe could do with some maintainers listed in the extra/recipe-maintainers section.
• The recipe must have some tests.
• The recipe must have a build/number section.
• There should be one empty line at the end of the file.

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/bad_recipe) and found some lint.

Here's what I've got...

For recipes/bad_recipe:

• The home item is expected in the about section.
• The license item is expected in the about section.
• The summary item is expected in the about section.
• The recipe could do with some maintainers listed in the extra/recipe-maintainers section.
• The recipe must have some tests.
• The recipe must have a build/number section.
• There are 2 too many lines. There should be one empty line at the end of the file.

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/bad_recipe) and found some lint.

Here's what I've got...

For recipes/bad_recipe:

• The home item is expected in the about section.
• The license item is expected in the about section.
• The summary item is expected in the about section.
• The recipe could do with some maintainers listed in the extra/recipe-maintainers section.
• The recipe must have some tests.
• The recipe must have a build/number section.
• There are 2 too many lines. There should be one empty line at the end of the file.
• Feedstock with the same name exists in conda-forge

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/bad_recipe) and found some lint.

Here's what I've got...

For recipes/bad_recipe:

• The home item is expected in the about section.
• The license item is expected in the about section.
• The summary item is expected in the about section.
• The recipe must have some tests.
• The recipe must have a build/number section.
• There are 2 too many lines. There should be one empty line at the end of the file.
• Feedstock with the same name exists in conda-forge
• Recipe maintainer "support" does not exist

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/bad_recipe) and found some lint.

Here's what I've got...

For recipes/bad_recipe:

• The home item is expected in the about section.
• The license item is expected in the about section.
• The summary item is expected in the about section.
• The recipe must have some tests.
• The recipe must have a build/number section.
• There are 2 too many lines. There should be one empty line at the end of the file.

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/bad_recipe) and found some lint.

Here's what I've got...

For recipes/bad_recipe:

• The home item is expected in the about section.
• The license item is expected in the about section.
• The summary item is expected in the about section.
• The recipe must have some tests.
• The recipe must have a build/number section.
• There are 2 too many lines. There should be one empty line at the end of the file.
• Feedstock with the same name exists in conda-forge
• Recipe maintainer "support" does not exist

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/bad_recipe) and found some lint.

Here's what I've got...

For recipes/bad_recipe:

• The "extra" section was expected to be a dictionary, but got a CommentedMap.
• The "package" section was expected to be a dictionary, but got a CommentedMap.
• The home item is expected in the about section.
• The license item is expected in the about section.
• The summary item is expected in the about section.
• The recipe could do with some maintainers listed in the extra/recipe-maintainers section.
• The recipe must have some tests.
• The recipe must have a build/number section.
• There are 2 too many lines. There should be one empty line at the end of the file.
• Recipe name has invalid characters. only lowercase alpha, numeric, underscores, hyphens and dots allowed
• The "package" section was expected to be a dictionary, but got a CommentedMap.
• The "extra" section was expected to be a dictionary, but got a CommentedMap.
• The "package" section was expected to be a dictionary, but got a CommentedMap.
• The "extra" section was expected to be a dictionary, but got a CommentedMap.

For recipes/bad_recipe:

• Recipe with the same name exists in bioconda: please discuss with @conda-forge/bioconda-recipes.

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/bad_recipe) and found some lint.

Here's what I've got...

For recipes/bad_recipe:

• The home item is expected in the about section.
• The license item is expected in the about section.
• The summary item is expected in the about section.
• The recipe must have some tests.
• The recipe must have a build/number section.
• There are 2 too many lines. There should be one empty line at the end of the file.
• Feedstock with the same name exists in conda-forge
• Recipe maintainer "support" does not exist

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/bad_recipe) and found some lint.

Here's what I've got...

For recipes/bad_recipe:

• The "extra" section was expected to be a dictionary, but got a CommentedMap.
• The "package" section was expected to be a dictionary, but got a CommentedMap.
• The home item is expected in the about section.
• The license item is expected in the about section.
• The summary item is expected in the about section.
• The recipe could do with some maintainers listed in the extra/recipe-maintainers section.
• The recipe must have some tests.
• The recipe must have a build/number section.
• There are 2 too many lines. There should be one empty line at the end of the file.
• Recipe name has invalid characters. only lowercase alpha, numeric, underscores, hyphens and dots allowed
• The "package" section was expected to be a dictionary, but got a CommentedMap.
• The "extra" section was expected to be a dictionary, but got a CommentedMap.
• The "package" section was expected to be a dictionary, but got a CommentedMap.
• The "extra" section was expected to be a dictionary, but got a CommentedMap.

For recipes/bad_recipe:

• Recipe with the same name exists in bioconda: please discuss with @conda-forge/bioconda-recipes.

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/bad_recipe) and found some lint.

Here's what I've got...

For recipes/bad_recipe:

• The home item is expected in the about section.
• The license item is expected in the about section.
• The summary item is expected in the about section.
• The recipe must have some tests.
• The recipe must have a build/number section.
• There are 2 too many lines. There should be one empty line at the end of the file.
• Feedstock with the same name exists in conda-forge
• Recipe maintainer "support" does not exist

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/bad_recipe) and found some lint.

Here's what I've got...

For recipes/bad_recipe:

• Failed to even lint the recipe, probably because of a conda-smithy bug 😢. This likely indicates a problem in your meta.yaml, though. To get a traceback to help figure out what's going on, install conda-smithy and run conda smithy recipe-lint . from the recipe directory.

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/bad_recipe) and found some lint.

Here's what I've got...

For recipes/bad_recipe:

• The home item is expected in the about section.
• The license item is expected in the about section.
• The summary item is expected in the about section.
• The recipe must have some tests.
• The recipe must have a build/number section.
• There are 2 too many lines. There should be one empty line at the end of the file.
• Feedstock with the same name exists in conda-forge
• Recipe maintainer "support" does not exist

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/bad_recipe, scripts/recipe) and found some lint.

Here's what I've got...

For recipes/bad_recipe:

• The home item is expected in the about section.
• The license item is expected in the about section.
• The summary item is expected in the about section.
• The recipe must have some tests.
• The recipe must have a build/number section.
• There are 2 too many lines. There should be one empty line at the end of the file.
• Feedstock with the same name exists in conda-forge
• Recipe maintainer "support" does not exist

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/bad_recipe) and found some lint.

Here's what I've got...

For recipes/bad_recipe:

• The home item is expected in the about section.
• The license item is expected in the about section.
• The summary item is expected in the about section.
• The recipe must have some tests.
• The recipe must have a build/number section.
• There are 2 too many lines. There should be one empty line at the end of the file.
• Feedstock with the same name exists in conda-forge
• Recipe maintainer "support" does not exist

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/bad_recipe) and found some lint.

Here's what I've got...

For recipes/bad_recipe:

• The home item is expected in the about section.
• The license item is expected in the about section.
• The summary item is expected in the about section.
• The recipe must have some tests.
• The recipe must have a build/number section.
• There are 2 too many lines. There should be one empty line at the end of the file.
• Feedstock with the same name exists in conda-forge.
• Recipe maintainer "support" does not exist

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/bad_recipe) and found some lint.

Here's what I've got...

For recipes/bad_recipe:

• The home item is expected in the about section.
• The license item is expected in the about section.
• The summary item is expected in the about section.
• The recipe must have some tests.
• The recipe must have a build/number section.
• There are 2 too many lines. There should be one empty line at the end of the file.
• Feedstock with the same name exists in conda-forge.
• Recipe maintainer "support" does not exist
• Please do not delete the example recipe found in (recipes/example/meta.yaml)

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/bad_recipe) and found some lint.

Here's what I've got...

For recipes/bad_recipe:

• The home item is expected in the about section.
• The license item is expected in the about section.
• The summary item is expected in the about section.
• The recipe must have some tests.
• The recipe must have a build/number section.
• There are 2 too many lines. There should be one empty line at the end of the file.
• Feedstock with the same name exists in conda-forge.
• Recipe maintainer "support" does not exist
• Please do not delete the example recipe found in recipes/example/meta.yaml.

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/bad_recipe) and found some lint.

Here's what I've got...

For recipes/bad_recipe:

• The home item is expected in the about section.
• The license item is expected in the about section.
• The summary item is expected in the about section.
• The recipe must have some tests.
• The recipe must have a build/number section.
• There are 2 too many lines. There should be one empty line at the end of the file.
• Feedstock with the same name exists in conda-forge.
• Recipe maintainer "support" does not exist

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/bad_recipe) and found some lint.

Here's what I've got...

For recipes/bad_recipe:

• The home item is expected in the about section.
• The license item is expected in the about section.
• The summary item is expected in the about section.
• The recipe must have some tests.
• The recipe must have a build/number section.
• There are 2 too many lines. There should be one empty line at the end of the file.
• Feedstock with the same name exists in conda-forge.
• Recipe maintainer "support" does not exist
• Please do not delete the example recipe found in recipes/example/meta.yaml.

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/bad_recipe) and found some lint.

Here's what I've got...

For recipes/bad_recipe:

• The home item is expected in the about section.
• The license item is expected in the about section.
• The summary item is expected in the about section.
• The recipe must have some tests.
• The recipe must have a build/number section.
• There are 2 too many lines. There should be one empty line at the end of the file.
• Feedstock with the same name exists in conda-forge.
• Recipe maintainer "support" does not exist
• Please do not delete the example recipe found in recipes/example/meta.yaml.
• The following maintainers have not yet confirmed that they are willing to be listed here: support. Please ask them to comment on this PR if they are.

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/bad_recipe) and found some lint.

Here's what I've got...

For recipes/bad_recipe:

• The home item is expected in the about section.
• The license item is expected in the about section.
• The summary item is expected in the about section.
• The recipe must have some tests.
• The recipe must have a build/number section.
• There are 2 too many lines. There should be one empty line at the end of the file.
• Feedstock with the same name exists in conda-forge.
• Recipe maintainer "support" does not exist
• Please do not delete the example recipe found in recipes/example/meta.yaml.

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/bad_recipe/meta.yaml) and found some lint.

Here's what I've got...

For recipes/bad_recipe/meta.yaml:

• The home item is expected in the about section.
• The license item is expected in the about section.
• The summary item is expected in the about section.
• The recipe must have some tests.
• The recipe must have a build/number section.
• There are 2 too many lines. There should be one empty line at the end of the file.
• Feedstock with the same name exists in conda-forge.
• Recipe maintainer "support" does not exist
• Please do not delete the example recipe found in recipes/example/meta.yaml.

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/bad_recipe) and found some lint.

Here's what I've got...

For recipes/bad_recipe:

• The home item is expected in the about section.
• The license item is expected in the about section.
• The summary item is expected in the about section.
• The recipe must have some tests.
• The recipe must have a build/number section.
• There are 2 too many lines. There should be one empty line at the end of the file.
• Feedstock with the same name exists in conda-forge.
• Recipe maintainer "support" does not exist
• Please do not delete the example recipe found in recipes/example/meta.yaml.

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/bad_recipe/meta.yaml) and found some lint.

Here's what I've got...

For recipes/bad_recipe/meta.yaml:

• The home item is expected in the about section.
• The license item is expected in the about section.
• The summary item is expected in the about section.
• The recipe must have some tests.
• The recipe must have a build/number section.
• There are 2 too many lines. There should be one empty line at the end of the file.
• Feedstock with the same name exists in conda-forge.
• Recipe maintainer "support" does not exist
• Please do not delete the example recipe found in recipes/example/meta.yaml.

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (conda_forge_webservices/tests/linting/data/recipe.yaml, recipes/bad_recipe/meta.yaml) and found some lint.

Here's what I've got...

For conda_forge_webservices/tests/linting/data/recipe.yaml:

This is a rattler-build recipe and not yet lintable. We are working on it!

For recipes/bad_recipe/meta.yaml:

• The home item is expected in the about section.
• The license item is expected in the about section.
• The summary item is expected in the about section.
• The recipe must have some tests.
• The recipe must have a build/number section.
• There are 2 too many lines. There should be one empty line at the end of the file.
• Feedstock with the same name exists in conda-forge.
• Recipe maintainer "support" does not exist
• Please do not delete the example recipe found in recipes/example/meta.yaml.

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/bad_recipe/meta.yaml) and found some lint.

Here's what I've got...

For recipes/bad_recipe/meta.yaml:

• The home item is expected in the about section.
• The license item is expected in the about section.
• The summary item is expected in the about section.
• The recipe must have some tests.
• The recipe must have a build/number section.
• There are 2 too many lines. There should be one empty line at the end of the file.
• Feedstock with the same name exists in conda-forge.
• Recipe maintainer "support" does not exist
• Please do not delete the example recipe found in recipes/example/meta.yaml.

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/bad_recipe/meta.yaml) and found some lint.

Here's what I've got...

For recipes/bad_recipe/meta.yaml:

• The home item is expected in the about section.
• The license item is expected in the about section.
• The summary item is expected in the about section.
• The recipe must have some tests.
• The recipe must have a build/number section.
• There are 2 too many lines. There should be one empty line at the end of the file.
• Feedstock with the same name exists in conda-forge.
• Recipe maintainer "support" does not exist
• Please do not delete the example recipe found in recipes/example/meta.yaml.
• Please do not delete the example recipe found in recipes/example/recipe.yaml.

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/bad_recipe/meta.yaml) and found some lint.

Here's what I've got...

For recipes/bad_recipe/meta.yaml:

• The home item is expected in the about section.
• The license item is expected in the about section.
• The summary item is expected in the about section.
• The recipe must have some tests.
• The recipe must have a build/number section.
• There are 2 too many lines. There should be one empty line at the end of the file.
• Feedstock with the same name exists in conda-forge.
• Recipe maintainer "support" does not exist

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/bad_recipe/meta.yaml) and found some lint.

Here's what I've got...

For recipes/bad_recipe/meta.yaml:

• ❌ The home item is expected in the about section.
• ❌ The license item is expected in the about section.
• ❌ The summary item is expected in the about section.
• ❌ The recipe must have some tests.
• ❌ The recipe must have a build/number section.
• ❌ There are 2 too many lines. There should be one empty line at the end of the file.
• ❌ Recipe maintainer "support" does not exist

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/12485720282. Examine the logs at this URL for more detail.}