POSTPONED - Upcoming Branch Renaming: Master to Main

[LuizMacedo]

We would like to inform you of an upcoming change to our repository. In an effort to adopt more inclusive terminology and adhere to industry best practices, we will be renaming our default branch from 'Master' to 'Main' on 05/12.

To ensure a smooth transition, we recommend taking the following steps to prevent issues and help with resolution in case you encounter any problems:

1. Update your local clone:
   • Before the change is implemented, fetch the latest changes from the remote repository by running git fetch origin.
   • Once the new "main" branch is live, run git checkout main to switch to the new branch.
2. Update your forks:
   • In your forked repository, create a new branch called "main" that tracks the upstream "main" branch: git checkout -b main --track origin/main.
   • Push the new "main" branch to your forked repository: git push -u origin main.
     3.Update your scripts and CI/CD pipelines:
   • Ensure that any scripts or CI/CD pipelines that reference the "master" branch are updated to use the "main" branch instead.
3. Rebase any active branches or pull requests:
   • If you have active branches or pull requests based on the "master" branch, rebase them onto the "main" branch to prevent any conflicts or issues.

In case of any issues or conflicts during the renaming process, please refer to the following GitHub documentation for resolving them:

• Renaming a branch
• Switching the base branch of a pull request

We understand that this change might cause some inconvenience, but we believe it is a necessary step towards fostering a more inclusive and welcoming environment. We appreciate your cooperation and support in making this transition as smooth as possible.

Should you need further assistance or have any questions, please don't hesitate to reach out to us by opening an issue in the repository or contacting us directly.

We appreciate your understanding and support as we implement this important change.

[LuizMacedo]

Due to the impact with automation, we need to plan a new timeline for the update.