- Wireframe
- Database schema
- Task Creation on Kanban
- Branch Naming Convention
- Creating a Pull Request on GitHub
View Details
The below database schema is designed by using dbdesigner. You can import this file room-booking.dbml into dbdesigner to visualize the db schema like the below image.
When creating a new task on the Kanban board, use the following naming structure for clarity and consistency: Convention
[<ServiceName>]<Task name>
- ServiceName: The name of the service in square brackets.
- Task name: A brief description of the task.
Example
For a task related to the Listing Service for updating the guideline document, the task name would be:
[Listing Service] Update guideline document
By following this structure, we enhance the readability and organization of our Kanban tasks, making it easier for the team to prioritize and manage work.
To maintain consistency and clarity in our branching strategy, we follow a specific naming convention for feature branches. This helps all team members understand the purpose of a branch at a glance.
Convention
feature/nodejs-msa-<itemid>-<title slug>
- feature: Indicates the type of branch (in this case, a feature development).
- nodejs-msa: Refers to the microservice architecture project for Node.js. : The unique identifier for the feature or task, such as a ticket number or item ID.
Example
For a task with item ID 1234 and a description Add login functionality, the branch name would be:
feature/nodejs-msa-1234-add-login-functionality
How to Obtain the Item ID?
After you've pushed your branch to the remote repository, follow these steps to create a pull request on GitHub: Navigate to the repository on GitHub.
- Go to the "Pull requests" tab.
- Click the "New pull request" button.
- Select the branch you created from the list of branches. This will be the branch you want to merge into the main branch.
- Provide a clear and descriptive title for the pull request. Typically, the title should match the branch name.
- Fill in the description with details about what changes are being proposed. Include context, screenshots, and references to related tasks or tickets.
- Assign reviewers, labels, or projects if necessary.
- Click the "Create pull request" button.
Following these steps ensures that your pull request is properly documented and ready for review by your team.
Example
The steps to create a pull request can be broken down as follows:
- Title: The title of the task from GitHub Projects or project management tool.
- Description: "This pull request adds login functionality to the Identity service..."
By following this structure, you make it easier for your team to understand and review your contributions.