Automate labelling Good First Issues

[KhudaDad414]

Reason/Context

As the Dashboard on the website is being completed, we need a way to automate labelling the good first issues.

Why

By automating the good first issue we achieve two things.

1. It will let us enforce this rule: every good first issue should have complexity and area labels as well.
2. It will make labelling good first issue easier.

How should it work

We should be able to label an issue by commenting these commands:
\good-first-issue javascript easy or \gfi javascript easy these commands should add three labels to the issue( good first issue area/javascript complexity/easy)

[github-actions]

Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

[fmvilas]

I like it. My only suggestion is that you use / (slash) instead of \ (backslash). Other than that 👍

I'm sure @derberg would want to know about this.

[derberg]

Like it! My only concern is, how do I remember what complexity levels we have. Maybe we should post a comment on each issue with the information about it, with example usage 🤔

btw @fmvilas you might want to know about this #94 😄

[KhudaDad414]

My only concern is, how do I remember what complexity levels we have. Maybe we should post a comment on each issue with the information about it, with example usage 🤔

@derberg Maybe after we implement it, I should write a script to comment on all the issues with good first issues label, saying to add the relevant information to the issue and how maintainers can do that using this command?
but we surely need to document these kinds of commands somewhere.

[fmvilas]

@derberg left a comment on #94. Pretty cool stuff.

My only concern is, how do I remember what complexity levels we have. Maybe we should post a comment on each issue with the information about it, with example usage 🤔

Complexity will always be subjective so I think it's ok to leave it at the owners' decision if something is easy or not. In any case, if something is a "good first issue", IMHO it should always be easy. The act of marking something as "good first issue" is also subjective. It's up to the contributor to decide if it's really a good first one for them or not.

[derberg]

but complex doesn't mean it is difficult. Complex means there is some clicking, adding files, running scripts, but in the end it is super super easy, just complex.

what I mean is, for consistency reasons, naming, we should have some list, otherwise, we will have a bunch of issues like complexity/easy or complexity/simple - area/javascript or area/java-script. So I don't want to decide on maintainer behalf what value they should provide, but they need to know what values are available to add, for consistency reasons

I should write a script to comment on all the issues with good first issues

this would be cool, like a reminder comment, "yo, you marked is as a good first issue, but we need more data from you", and we could use annotations to mention people that create a comment, so they get notification