stubsabot: add project links

[hauntsaninja]

See #8157 for an example

[JelleZijlstra]

Nice, thanks

[Akuli]

I have never understood these instructions. Why not just fix the PR by pushing commits directly to it, and merge when stubtest passes again?

[AlexWaygood]

Yes, that seems to be the more common rhythm we're settling into.

[hauntsaninja]

It's a good question. It's because of what the current code will do if we run it automatically on a regular basis (rather than me running it manually in batches). stubsabot.py just makes a commit off of master and pushes it. master changes regularly, so these pushes would fail. Rather than failing, silently doing nothing, or some more complicated logic that checks what's on the remote, it currently force pushes to the remote:

typeshed/scripts/stubsabot.py

Line 283 in a9fb8c5

subprocess.check_call(["git", "push", "origin", branch_name, "--force-with-lease"])

So this means it could undo changes we made.

But thinking about it a little bit more, silently doing nothing might not be that bad an option?

The other reason for these instructions is in theory non-maintainers could contribute (and they might benefit from instructions more so than maintainers).