generated from 2025/project_base
Refactor/Restructure the structure of Repo #6
Labels
No labels
ADMIN DASHBOARD TASKS
AUDIT SERVICE TASKS
ROLE-BASED ACCESS CONTROL
USER LIFECYCLE TASKS
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
1 participant
Notifications
Due date
Dependencies
No dependencies set.
Reference
2025/Group_2_IAM_SYSTEM#6
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
By the end of tomorrow (2025-11-21), everyone should already have a designated role on the team and should start working on a project.
Everything in the repo right now is under question for change.
Initial plan:
Initial Suggestion for Each Microservice Structure:
Real Example: src/services/user-service (message was written while
47514e19e3was the last commit to that microservice)Oh, and we should probably do another folder on the top layer for Frontend