Conda-forge.github.io: Explain how to accept conda-forge invitation

[jakirkham]

Quite frequently we find ourselves explaining how to accept a GitHub organization invitation. Given this, we should add it to the docs. Possibly with links to relevant GitHub pages. That way we can reference it when it comes up again.

[djsutherland]

I think it would probably be good to have a little bit more in general of "my pull request's been merged, now what?" docs, including this, that we can just link to when we merge a staged-recipes PR. Basically also saying that the feedstock repo will be made, but it might take a little while, etc etc.

[kain88-de]

Those docs could also directly link to an article to update the package later.

[jakirkham]

Stealing from @isuruf, maybe we can add this link: https://github.com/orgs/conda-forge/invitation

[jakirkham]

Also have had luck telling people to go to the org webpage and look for invite details in the banner at the top.

[leycec]

@jakirkham has the exact right of it.

Despite having successfully received GitHub organization invitations in the past, I failed to receive either a confirmatory e-mail or a GitHub notification for the conda-forge invitation. Which meant that I then had to waste everyone's time yet again by complaining like a miserable sea hag. To lazily copy-pasta myself:

According to a pertinent StackOverflow thread (again generously supplied by @isuruf), this really is a widespread GitHub API and/or UX issue. Organization invitations occasionally fail non-deterministically, for reasons no one knows. Some GitHubbers sporadically get hit by it. Some don't.

On the bright side, this isn't conda-forge's fault. On the dark side, you probably want to publish that link. A FAQ entry might be the short-term answer; an automated comment appended to the bottom of any newly accepted pull request might be the long-term answer.

[jakirkham]

So we now have an automated welcome message thanks to @isuruf's work. 🎉

Here's an example of a recent one. We can tweak that message. We can also add something in the docs that we link to from that message.

Please share your thoughts. :)

[leycec]

This is indeed fantastic. Appending message text specific to each new user (if any) was a mystifyingly clever stroke of genius. You even handled the obnoxious edge case of English plurals properly. Aside from the lack of support for Klingon localization, I am left without complaints. ^{_How can it be?_}

Let us rejoice on this rare occasion. Bravo, @isuruf and @jakirkham!