fix: Add push and pull section in Git config

[mdsanima]

Configured git to use the simple pushing strategy and to rebase instead of merge on pull, optimizing the workflow and reducing merge conflicts. This setting makes push defaults safer and pull updates cleaner by rebasing local changes on top of fetched commits.

The provided code diff represents an update to the .gitconfig file, which is a configuration file for Git, the version control system. The changes made to this file are meant to address specific behaviors of Git in relation to push and pull operations.

Here's what has changed:

1. A new section called [push] has been added to the Git configuration file with the setting default = simple. This setting modifies Git's behavior when pushing changes to the remote repository, ensuring that only the current branch is pushed to the remote branch that it tracks, which simplifies working with remote branches and prevents the potential for errors when multiple branches are involved. This is especially useful when using Git in a collaborative environment, making sure that team members only push the relevant changes.

2. Another section called [pull] has been introduced with the configuration rebase = true. This alteration affects how Git pulls updates from a remote repository. Specifically, when set to true, this option tells Git to rebase local commits on top of the fetched branch commits. The rebase strategy is a cleaner alternative to merge commits as it creates a linear history, which makes it easier to follow the commit history and avoid potential merge conflicts.

Both these changes are likely meant to standardize and streamline the workflow for developers using this repository. These configurations make it so that when any developer is pulling changes from or pushing changes to the repository, the process is more predictable and manageable, leading to fewer conflicts and a cleaner commit history. This fits with the author's context note that mentioned this is a fix to add push and pull sections, suggesting they were included in response to identified needs for improved Git operation behaviors within the project.

For a reviewer, this evidence of proactive configuration helps to understand that the goal of these changes is to prevent common problems such as complicated merges or inadvertent pushing of multiple branches. It enhances both individual and collaborative efforts in version control management.