Closed SiddheshKukade closed 1 year ago
Discussion link : #649
This issue is created to add a page in the docs explaining how issues and labeling works in talawa, Something like: https://handbook.rocket.chat/departments-operations/support/github-issues but in a more detailed manner.
This issue did not get any activity in the past 10 days and will be closed in 365 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue.
/cc @palisadoes , @DMills27 , @tasneemkoushar , @noman2002 I'm thinking about adding them to all the repos. I'll add them and then we can improve the labels accordingly from the contributors feedback and experience.
@SiddheshKukade I appreciate this idea and its use, I just want to caution you that it may not be sustainable from the volunteers side of things to keep up with this accurately and effectively.
This issue did not get any activity in the past 10 days and will be closed in 365 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue.
This is completed and the labels can now be used and are available at the following links
Is your feature request related to a problem? Please describe. As the contributors to the talawa projects are increasing drastically year after year there are a lot of changes that are being added, changes or fixed everyday. Having some customized issues labels for our talawa apps and APIs would be great to links issues together and track them as parent of children of each other
Describe the solution you'd like I'd like to extend the issue labels with the following:
For Talawa-docs
technical
: adding docs related to the technicalities of the talawa apps.user-guides
: for adding docs related to onboarding new users, explaining new concepts in a non technical way,etc.design
: realted to the design of the docs websitemisc
: for other miscellaneous issuesFor Talawa-admin, API and Mobile
COLORED IN LIGHTGRAY
parent
: The issue is generating more sub-issueschildren
: The issue which is generated due to other parent issue.COLORED IN YELLOW
figma
: issue related and being worked with the figma file of the Admin UIALL COLRED IN PURPLE
area/performance
: related to improving performance of websitearea/ci-cd
: relted to CI/CD workflowarea/tests
: related to adding testsarea/ux
: relted to UX improvementscomponent/api
: Issues related to the talawa APIALL COLORED IN WHITE
issue/blocked
: blocked due to another pending problem.issue/design-required
: Design template is require before proceedingissue/blocked
: remind tag to check issue in the future time (basically means issue is not relevant right now)issue/stale
: problem desribed is stale or outdated.PR labels:
ALL COLORED IN LIGHT BLUE
pr/do-not-merge
: Can't merge due to merge-conflicts of files or a important review is required.pr/on-hold
: if the linked issues is on holdpr/dependancies
: related to adding dependancies in the projectDescribe alternatives you've considered Please suggest alternatives in comments
Approach to be followed (optional) IMPORTANT: Someone with a member access to the Palisadoes Foundation is required to add the issue lables in each repo with the description