Think about an action that periodicaly checks emotions on issues

[derberg]

Reason/Context

I do not like, as a user, when I get into some project, I see there was some important issue for the community, but it is either closed or opened forever, but people do not write anything but only share their emojis, thumbs up and others.

The expectation is that maintainers will see that, and frustration arises.

But come one, how could maintainers even see every single issue and all those emotions if you do not approach them directly 🤷🏼

Description

Please try answering few of those questions

• maybe a github action in every repo that calls API on every issue and PR in a given repo and checks emojis
• have some settings like, report only issues and PRs with more than 5 emotions or something like that
• ping us on slack as we do now with new issue or pr, or releases

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity 😴
It will be closed in 60 days if no further activity occurs. To unstale this issue, add a comment with detailed explanation.
Thank you for your contributions ❤️

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity 😴
It will be closed in 60 days if no further activity occurs. To unstale this issue, add a comment with detailed explanation.
Thank you for your contributions ❤️

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity 😴
It will be closed in 60 days if no further activity occurs. To unstale this issue, add a comment with detailed explanation.
Thank you for your contributions ❤️

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️

[derberg]

/help

[asyncapi-bot]

Hello, @derberg! 👋🏼

I'm Genie from the magic lamp. Looks like somebody needs a hand! 🆘

At the moment the following comments are supported in issues:

• /good-first-issue {js | ts | java | go | docs | design | ci-cd} or /gfi {js | ts | java | go | docs | design | ci-cd} - label an issue as a good first issue.
  example: /gfi js or /good-first-issue ci-cd

[derberg]

/gfi ci-cd

[derberg]

@KhudaDad414 look ☝🏼 it works 🚀

[darp99]

Hello sir , @derberg

How can i start work on this issue ?

[derberg]

@darp99 hey! Most important questions what is your experience with GitHub Actions. I need to know so I can suggest how to start. This issue with also require you to use GitHub REST or GraphQL API. You do not need to know much about APIs though as they provide client library.

[darp99]

Sorry i don't want to disappoint you. i haven't used Github Action but i am exploring it. I know the REST API very well
Please guide me. what i have to do. i will learn if something is missing and try to give my best

[derberg]

Sorry i don't want to disappoint you

no worries, you definitely did not disappoint me. I just wanted to understand how deep in details should I go.

My advice, for now, forget about GitHub Actions -> these are the easiest in this task. More important is to figure how to do this calculation with, either GitHub REST API or GraphQL API

From GitHub Action point of view what you need to know for your research is:

• such action, that measures emotions will run in every single repo separately, so you need to figure how to check emotions on issues, PRs and discussions on repo level
• and yeah I don't think anything more is needed 🤔

Once you have it, I will help with GH Actions. We can even schedule a call if you want

@KhudaDad414 any advice from your side? you did something similar when you worked on the dashboard concept, the HOT-ness of issue.

[KhudaDad414]

not much, I just wanted to add: the Graphql repository query can be used to parse all of the reaction groups of every PRs, issues and discussions with a single Graphql query 😀

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️

[sparsh-989]

Hey,
Can I work on this issue?

[14Richa]

Hey @derberg!

I am working on a draft PR, and I think it would be good to flesh out more details. The way I see it currently -

1. Have an action that counts the emojis in each issue/PR.
2. Make that action comment on the issue/PR tagging the relevant person (need to figure this out how to find this - maybe the person who recently merged in code from the same repo?). We need this comment so that we don't keep iterating on the same issue/PR. Once the comment is added, this issue will not come up in the first filter.
3. Ping the person found in 2 on slack once.

What are your views about this?

[derberg]

How about adding a label instead of comment?

Also, later we can enhance it with steps about dropping some message in slack and stuff like that. Label should solve problem of duplication and also enable us to quickly filter out all emotional issues and PRs

[pragya-20]

Hi @derberg
I have contributed to this issue via this PR. Looking forward to your feedback.

[derberg]

@pragya-20 please next time check previous conversations, check if PRs are already opened and how active they are. We have plenty of work here, let's avoid duplication of efforts. Also maintainers, at least maintainers like me, do not like to close PRs like #222 as I know you spent some time on it, and it basically feels bad to close it, even though there is no other option. I hope you understand 🙏🏼

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️

[Shurtu-gal]

Hey @derberg,
I was going through the PR raised by both @pragya-20 and @14Richa, especially #220 with all the comments and suggestions. Is this issue still relevant, and if yes is @14Richa still working on this?

[derberg]

nobody is working on it atm, and @14Richa is not actively contributing for like a year now