move osslifecycle and nycrc into /github

[chris48s]

As noted in #5234 these two anomolies should be moved into the /github dir and URL namespace, like all the other "get a file from a github repo and extract a value" badges. We should set up redirects for compatibility.

[calebcartwright]

I know those two badges only support looking for their respective files in github today, but is there any reason that has to be the case? For example I could just easily use Bitbucket and nyc and want the badge. I know we haven't had any asks for those just yet, but perhaps worth considering.

[chris48s]

Hmm.. that's broadly also true of all the other "get a file from a github repo and extract a value" badges. i.e:

• github-go-mod
• github-all-contributors
• github-lerna-json
• github-pipenv
• github-manifest
• github-package-json

Whichever way we look at it, we should treat osslifecycle and nycrc the same as all of those, but maybe there is a case that none of those should be github-specific

[calebcartwright]

Excellent point!

Maybe in a perfect world we'd have a "get a file from (VCS provider) and extract a value" framework/reusable functions or base classes.

[calebcartwright]

And just to clarify, I don't have any objections to moving these services under the github directory, regardless of what we may or may not do down the line. At this point it's really more about easily knowing where all the service classes are that use the GitHub APIs to do their thing.

[chris48s]

Another relevant consideration here
#9516
adds a badge that just takes an arbitrary file (not hard-coded to GitHub). One of the issues here is: How these fit into the URL schema?