MOBILE: Automatic Labeling for Dependencies, Security and Design Related Issues

[palisadoes]

Is your feature request related to a problem? Please describe.

1. We spend a lot of time manually labeling issues that are created.
2. Automation will significantly reduce this overhead

Describe the solution you'd like

Using the auto-label GitHub action that we currently use: https://github.com/marketplace/actions/auto-label

1. Make configuration changes to the existing issue.yml file.
2. Do not rename the existing issue.yml file.
3. Dependencies
   1. When the words dependabot, dependency or dependencies are in the body of the issue
   2. Add the labels dependencies, security and good first issue
4. Security
   1. When the word security are in the body of the issue
   2. Add the label security and good first issue
5. Design
   1. When the words layout, screen, design or figma are in the body of the issue
   2. Add the label ui/ux and good first issue

Describe alternatives you've considered

• See above

Approach to be followed (optional)

• See above
• No other functionality must be affected

Additional context

Related Issues. The same person must be assigned to both:

• https://github.com/PalisadoesFoundation/talawa-admin/issues/2256
• https://github.com/PalisadoesFoundation/talawa/issues/2555

Potential internship candidates

Please read this if you are planning to apply for a Palisadoes Foundation internship

• https://github.com/PalisadoesFoundation/talawa/issues/359

[VanshikaSabharwal]

@palisadoes Please assign me this issue. I am willing to modify the issue.yml file to automatically label issues based on the specified keywords

[github-actions[bot]]

This issue did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue.

[VanshikaSabharwal]

i have raised PR. https://github.com/PalisadoesFoundation/talawa/pull/2557

[github-actions[bot]]

This issue did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue.

[VanshikaSabharwal]

I have raised PR and i am working on it. #2557

[github-actions[bot]]

This issue did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue.

[palisadoes]

unassigning. inactivity

[heropj]

Hi @palisadoes, I would like to work on this issue. I can make the necessary changes to the issues.yml file as described and resolve it efficiently. Could you please assign this issue to me? Thank you!

[SXUBXAM]

Hi @palisadoes,

I hope this message finds you well. I have forked the repository on my GitHub, resolved the issue, and successfully tested it in my environment. Everything is functioning perfectly. Would you kindly assign this task to me?

Additionally, I attempted to make changes directly in the issues.yml file; however, I encountered authorization issues due to the PR guidelines. As an alternative, I explored a different approach, which successfully resolved the issue.

Thank you!

[ARYPROGRAMMER]

@palisadoes can i work on this. Seems like I have an optimised approach for this