Run new conda_forge lints

[isuruf]

No description provided.

[jakirkham]

Pushed this to the repo for you so that it can be tested (requires a GitHub token for some of the tests).

[isuruf]

I'm sorry, how do I test it?

[jakirkham]

By pushing the branch to this repo directly. Have just added you to conda-forge/conda-forge-webservices so that you can do this as needed.

[jakirkham]

Should add that I pushed these changes to the branch isuruf/lint on this repo.

[isuruf]

And if I add a recipe to the root, it would automatically check the recipe?

[jakirkham]

It searches for anything that looks like a recipe (has a meta.yaml). We put these in PRs like this one. Though it might be worth building off of existing PRs to cutdown on the number of these we create (if possible). There are checks for the message that one gets, which are the most useful. Though we also have integration tests that comment on the PR if needed.

[isuruf]

@jakirkham, can you explain what I have to do? Btw, these lints are checked in conda-smithy.

[jakirkham]

So if you have already changed the bad recipe, would update the message in the bad recipe test.

Were there any things that we weren't testing in conda-smithy that would require a token? If so, this is something we should try testing here.

[isuruf]

Changed bad_recipe again to check one more lint that needed GH_TOKEN. I'll update the test

[jakirkham]

LGTM. Thanks @isuruf.

[isuruf]

Tests pass. Merging.

[isuruf]

Does this get deployed immediately?

[jakirkham]

It is suppose to build and deploy on Heroku after you merge. Though I don't think it has. Triggering manually.

[jakirkham]

Should now be deployed.