Distributed Development

Distributed development using Git has become increasingly popular in recent years due to its flexibility and scalability. Here are some best practices to follow when using Git for distributed development: 

• Use a clear and consistent branching strategy: Establish a clear and consistent branching strategy that fits your team's workflow. Git Flow, GitHub Flow, and GitLab Flow are popular branching models. 
  
• You can read through Git flow workflow to get deeper understanding on the flow. 
• Use descriptive commit messages: Write clear and descriptive commit messages that accurately describe the changes made in each commit. Use the imperative mood and keep them short (around 50 characters or less). 
• Merge changes regularly: Merge changes from the upstream branch (e.g., master) regularly to ensure that your branch stays up to date and that merge conflicts are minimized.  
• Use pull requests: Use pull requests (or merge requests) to review changes before they are merged into the upstream branch. This helps catch potential issues and ensures that the code meets the project's standards. 
• Keep your repository clean: Avoid committing unnecessary files (e.g., binaries, logs) or sensitive information (e.g., passwords, API keys). Use a .gitignore file to exclude files that should not be committed. 

Practice - https://learngitbranching.js.org/