docs: workflow to add labels on analyzing title/comment based on conditions

[Anmol-Baranwal]

• Reference: https://github.com/hoho4190/issue-pr-labeler

Related Issue

Closes #501

About Regex Expression

You can test it here: https://regex101.com/

I am taking two examples, which you must read so that you can properly review the PR.

• /\bfeat\b/: This regular expression matches the exact word "feat" with word boundaries (\b). It will match strings that contain the word "feat" as a whole word, but not if it's part of another word (e.g., "defeat" or "feature").

• /feature/i: This regular expression matches the word "feature" (case-insensitive) anywhere within a string. It will match strings that contain "feature" in any combination of uppercase and lowercase letters (e.g., "Feature", "FEATURE", "feature").

Describe the changes you've made

• I have checked issue forms and corresponding labels to properly use the config workflow.
• I have not made this workflow for analyzing issues, so let me know.
• I didn't found anything related to adding multiple labels at once, so I have used 1 label for 1 set.
• add labels in the repository used in the config file or suggest any changes.

Let me know if you need anything.
Good luck :)

Type of change

What sort of change have you made:

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Code style update (formatting, local variables)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update.
• This change requires a documentation update

How Has This Been Tested?

• My code follows the guidelines of this project.
• I have performed a self-review of my own code.
• I have commented on my code, particularly wherever it was hard to understand.
• I have made corresponding changes to the documentation.
• My changes generate no new warnings.
• I have added tests that prove my fix is effective or that my feature works.
• Any dependent changes have been merged and published in downstream modules.

Code of Conduct

• I agree to follow this project's Code of Conduct

[vercel]

@Anmol-Baranwal is attempting to deploy a commit to the Vibey Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

Thank you, @Anmol-Baranwal, for creating this pull request and contributing to GitHub-ReadMe!
Our review team will thoroughly review the pull request and will reach out to you soon!
Please make sure you have marked all the completed tasks as done.
We appreciate your patience and contribution!

[github-actions]

Thank you for creating a pull request for vibey!

We appreciate your contribution and are excited to review your changes. If you have any questions or need additional information, please don't hesitate to let us know. We look forward to working with you to improve vibey. Thanks again for your support!

If you want to keep contributing to open source and want to do it with a supportive and inclusive community, consider joining UniKonf. We help and encourage each other to make regular contributions to open source projects. If you have any questions, do not hesitate to ask. We look forward to having you as part of our community!

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
vibey	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Aug 1, 2023 11:24am

[Deepu178]

you should check the errors.

[Anmol-Baranwal]

you should check the errors.

Let me double check it. I will let you know.

[Anmol-Baranwal]

I believe this would work. Earlier, I was trying to take issues into account, but I hadn't given read permission for the same. Due to this, an error was arising in the CI activity.

[Deepu178]

@Anmol-Baranwal there was no issue with your code. you can checkout in above screen by building it locally.

[Anmol-Baranwal]

@Anmol-Baranwal there was no issue with your code. you can checkout in above screen by building it locally.

Yeah, it is running as usual.

[Deepu178]

Thanks for your contribution @Anmol-Baranwal and looking for more contribution in gh actions.