Automate skill label generation

[dhruvkb]

Problem

Skill labels need to be manually set up in skills.json. This

• increases manual work on the part of repo maintainers to ensure that the skills listed in a different repo (this one) are up to date
• causes redundancy of information that is already present in cc-metadata.yml under the technologies key in each repo

Description

The technologies key could be expanded to a more verbose structure to describe languages, libraries and frameworks and then used to eliminate the need for skills.json entirely. This presents benefits such as

• richer information about the technological make-up of our projects
• automated sync of labels with technologies

Alternatives

The improvements to .cc-metadata.yml can be a good-to-have part of the feature if there isn't a consensus to proceed with that. But the automation of skill labels is still beneficial. Also it does not have to be binary, a combination of .cc-metadata.yml and skills.json would also be a fine solution.

Implementation

• I would be interested in implementing this feature.

[kgodey]

I think it makes sense to build the skills based on .cc-metadata.yml and expand the technology list there.

I wonder if we could also encode branch protection in .cc-metadata.yml instead of storing it here, that way all configuration related to a repo could live in that repo. That should be a separate ticket though.

[Cronus1007]

@dhruvkb Shall i implement this one.

[dhruvkb]

Yeah @Cronus1007, please do! But let's start with a plan on how the .cc-metadata.yml file will look like before starting development.

[Cronus1007]

@dhruvkb Here what I am planning that first of all let us make a request on https://api.github.com/orgs/creativecommons/repos and then get all the pinned repositories. Then we can proceed to get the first three most prioritized technologies of the pinned repos.

[dhruvkb]

The skill label generation has to work on all CC repositories, not just the first one. Also why just the first three technologies and not all of them?

Another important consideration is regarding language and framework/library. For example, someone who is quite familiar with JavaScript might still experience some problems if the issue is very Vue-oriented... so the frameworks have to be factored in when building labels.

[Cronus1007]

@dhruvkb Let me a build a seperate folder for this and initialize this project by eod or should I build a local repo.

[Cronus1007]

Set the ADMIN_GITHUB_TOKEN environment variable with your GitHub token.
You will need a GitHub token with admin permissions to the creativecommons
GitHub organization.

Any opinoin regarding this?