What version control practices do you follow when working with a team on a GitHub project?

1. Fork the Repository: The first step is to create a personal copy of the project on your GitHub account. This is known as "forking" the repository.

2. Clone the Repository: After forking, you need to clone the repository to your local machine. This allows you to work on the project locally.

3. Create a New Branch: Before making any changes, it's a good practice to create a new branch. This keeps your work separate from the main project and allows you to work without affecting the main project.

4. Make Changes and Commit: After creating a new branch, you can start making changes to the project. After making changes, you need to commit them. This saves your changes locally.

5. Push Changes to GitHub: After committing your changes, you need to push them to your forked repository on GitHub.

6. Create a Pull Request: Once you've pushed your changes to GitHub, you can create a pull request. This is a proposal to the original repository to include your changes. The project maintainers can review your changes and decide whether to include them or not.

7. Code Review and Merge: The project maintainers will review your changes. If they approve your changes, they will merge them into the main project. If they have any feedback or require changes, they will let you know.

8. Pull from Upstream: It's important to keep your local repository up-to-date with the main project. You can do this by pulling from the upstream repository.

9. Repeat: You can repeat this process for every change you want to make to the project.

These are the basic version control practices you should follow when working with a team on a GitHub project.