LABEL CHECKER: Add automated labels for new opened issues

[KAUR1984]

Description

Set up GitHub workflow which automatically gives a gentle reminder to add labels to newly opened issues. It acts as a sanity check to ensure consistent and well-documented issues in Hive Docs.

This workflow should run on the issues: [opened] event and only adds a comment if the issue has zero labels after 30 minutes from the time of creation. This time buffer is to avoid adding comments - before the developer has finished writing the full issue.

Why

Currently, new issues remain unlabelled after being opened. This issue does not address the project labels such as Priority and Estimated Effort yet. Could address them in separate issues if needed. Adding labels on issues are very easy to miss, hence this intends to help developers with these sanity checks.

Why Labels are important?

Ref: https://www.geeksforgeeks.org/git/what-is-github-labels/

1. They help organise and categorise issues, and gives an instant overview of the issue.

   • bug -> something broken,
   • feature -> new functionality,
   • docs -> documentation improvement.

2. Labels help with automation

   • Labels act as signal for trigger automation.
   • Ex. Do ... when bug label is added.
   • Ex. Add a comment if no labels exists in the issue.

3. Prioritise team's attention

   • Using high, medium and low priority labels.
   • Ex. Which high-priority issues are unassigned?

Nice to Haves

1. Delete the comment automatically after labels are added. In future PRs.
2. Avoid the sleep time as it ties up the runner unnecessarily. This is intended to give developers some time to edit the issue before bot commenting. Might use alternative approaches in future PR for sleep job improvement.

Close Criteria

• Create a well-documented workflow for checking labels on issues.

[KAUR1984]

Latest edit -- added nice to haves in the issue description.

[KAUR1984]

As per the discussion in Hive Docs, it might be better use if we add automated labels to issues. There are some existing workflows we could use for that. Would create a PR once the changes are ready to review.