DOC: Add instruction to make a new branch from 'main'

[matthewfeickert]

• Multiple people forget to do this when trying to add recipes and then run into trouble, so add an explicit instruction to create a new branch.

Checklist

• Title of this PR is meaningful: e.g. "Adding my_nifty_package", not "updated meta.yaml".
• [N/A] License file is packaged (see here for an example).
• [N/A] Source is from official source.
• [N/A] Package does not vendor other packages. (If a package uses the source of another package, they should be separate packages or the licenses of all packages need to be packaged).
• [N/A] If static libraries are linked in, the license of the static library is packaged.
• [N/A] Package does not ship static libraries. If static libraries are needed, follow CFEP-18.
• [N/A] Build number is 0.
• [N/A] A tarball (url) rather than a repo (e.g. git_url) is used in your recipe (see here for more details).
• [N/A] GitHub users listed in the maintainer section have posted a comment confirming they are willing to be listed there.
• [N/A] When in trouble, please check our knowledge base documentation before pinging a team.

[matthewfeickert]

@conda-forge/staged-recipes, ready for review!

[github-actions]

To help direct your pull request to the best reviewers, please mention a topic-specifc team if your recipe matches any of the following: conda-forge/help-c-cpp, conda-forge/help-cdts, conda-forge/help-go, conda-forge/help-java, conda-forge/help-julia, conda-forge/help-nodejs, conda-forge/help-perl, conda-forge/help-python, conda-forge/help-python-c, conda-forge/help-r, conda-forge/help-ruby,or conda-forge/help-rust. Thanks!

[mfansler]

I think this is a good recommendation. However, I'll defer to others for merging.

Also, worth noting that this simply brings the README here into harmony with the documentation: https://conda-forge.org/docs/maintainer/adding_pkgs/#step-by-step-instructions

[matthewfeickert]

Also, worth noting that this simply brings the README here into harmony with the documentation: https://conda-forge.org/docs/maintainer/adding_pkgs/#step-by-step-instructions

That alone is worth it. (Some) people realistically aren't reading the maintainer docs before coming here, but if that's the goal then it should be made much more prominent than a link in step 2 of high level instructions in the README

staged-recipes/README.md

Line 18 in 8a71ace

2. Make a new folder in `recipes` for your package. Look at the [example recipe](recipes/example), our [documentation](http://conda-forge.org/docs/maintainer/adding_pkgs.html#) and the [FAQ](https://github.com/conda-forge/staged-recipes#faq) for help.

[ocefpaf]

The linter is probably stuck b/c it is looking for a recipe. Merging this... Thanks!