Avoid owner's reply too

[dpnkrpl]

Need to avoid owner's reply too. It should not comment back on issues raised by the owner. Also replying back to the owner's further comments. Over all it should comment for the first time only to the original issue raiser.

Originally posted by @krazy4code in #37 (comment)

[issue-label-bot]

Issue-Label Bot is automatically applying the label feature_request to this issue, with a confidence of 0.59. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

[github-actions]

Hi, @krazy4code,
Thanks for your contribution 💙 .
Contributors 🧑‍🤝‍🧑 like you make the open source community 🌍 such an amazing place to learn 📖 , inspire 👼, and create 🎨 .
We will investigate 👀 and get back to you as soon as possible 👍 . Just make sure you have given us sufficient information ℹ️.

By that time enjoy this joke 👇 , hope you like it 😄

"We messed up the keming again guys."

Use this action on your projects.

[github-actions]

Hi, @deep5050,
Thanks for your contribution 💙 .
Contributors 🧑‍🤝‍🧑 like you make the open source community 🌍 such an amazing place to learn 📖 , inspire 👼, and create 🎨 .
We will investigate 👀 and get back to you as soon as possible 👍 . Just make sure you have given us sufficient information ℹ️.

By that time enjoy this joke 👇 , hope you like it 😄

Java is like Alzheimer's, it starts off slow, but eventually, your memory is gone.

Use this action on your projects.

[github-actions]

Hi, @deep5050,
Thanks for your contribution 💙 .
Contributors 🧑‍🤝‍🧑 like you make the open source community 🌍 such an amazing place to learn 📖 , inspire 👼, and create 🎨 .
We will investigate 👀 and get back to you as soon as possible 👍 . Just make sure you have given us sufficient information ℹ️.

By that time enjoy this joke 👇 , hope you like it 😄

Why are modern programming languages so materialistic?
Because they are object-oriented.

Use this action on your projects.

[deep5050]

okay, labeling and commenting back on an issue also causing the workflow to run. That's a serious issue.

[deep5050]

This might solve the issue.

https://docs.github.com/en/free-pro-team@latest/actions/reference/events-that-trigger-workflows#issues
https://docs.github.com/en/free-pro-team@latest/actions/reference/events-that-trigger-workflows#pull_request

planning workflow to run only on:

1. issue opened/reopened
2. pull_request opened/reopened