We can Rename the current local Git branch name by, • Switch to the main via the command git checkout master. • Enter the following command to rename a Git branch git branch -m old-name new-name . • To ensure that the rename was successful, retrieve the current status of the branch using the git branch -a.

We can Rename the current local Git branch name by, • Switch to the main via the command git checkout master. • Enter the following command to rename a Git branch git branch -m old-name new-name . • To ensure that the rename was successful, retrieve the current status of the branch using the git branch -a.

If we import a server component inside a client component, it will be treated as a client component but if we pass a server component to a client component as a child prop, it will not be converted to the client component and will be treated as a server component. This gives more granular control on what to show at what component. Composable child components will still be treated as client components as it is not passed as a child to the client component.

while upgrading your rails api only app to support html views , make sure to run rails assets:precompile in your local so that your assets are served properly and also make sure your assets are properly linked in assets/configs/manifest.js , or the process will be aborted. If we skip this step, and it has some errors, it will cause build failures.

while updating ruby version in an existing app, make sure to also update the ruby version in your Dockerfile, or else it will cause build failure.

while creating rubocop github action , we need to add two flags: • fail_on_error: true -> which will exit the process when error occurs • filter_mode: noFilter -> this will run the rubocop for the entire project directory

Removing swap files form the merge -: we can can use our terminal for that we have to just ad the changes to the git then commit them with a message and then push the changes to repo and it will automatically reflect on the merge request.

Removing swap files form the merge

The basic principles for User Interface design

1. Hierarchy: User should be able to distinguish between important and less important information at a glance. The UI hierarchy should highlight what the user cares about the most.
2. Contrast: To draw attention to important content or features.
3. Alignment: Proper alignment helps with readability.
4. Clarity: There should not be anything that will confuse the user. We should try to provide a design that user can understand easily by taking a glance at it.
5. White space: For a design to work better. It needs to have a adequate amount of space between it's content.

```Add the :environment task as dependency for Rake task to access models.

desc "count number of users" task :count_users do puts User. count # NameError: uninitialized constant User (NameError) end

To make the models available, tell Rails to load the environment before running the task. desc "count number of users" task count_users: [:environment] do puts User. count end```