Can I fork a repository multiple times

[reshamsai150]

if I raised the issue in the same repository to which I have already contributed then should I fork the repository or use the existing one which I have already forked

[RishabhDhawad]

If you're already contributing to a repository, there's no need to fork it again just to raise an issue.

[aryansharma220]

If you have already forked the repository and want to contribute to the same project, you should use the fork you already have. There's no need to create a new fork.

The typical workflow for contributing to an open-source project using a fork is:

1. Fork the main repository to your GitHub account (you've already done this step).
2. Clone your forked repository to your local machine.
3. Create a new branch for your changes.
4. Make your changes and commit them to the new branch.
5. Push the new branch to your forked repository on GitHub.
6. Create a new Pull Request from your forked repository's branch to the main repository's main branch (usually called main or master).

The maintainers of the main repository will review your Pull Request and provide feedback or merge your changes if everything looks good.

By using your existing fork, you can continue to work on the same project and create new branches for different issues or features you want to contribute. This way, you don't have to create a new fork every time you want to make a contribution.

[Ojas-Arora]

If you have already forked the repository and have made contributions through that fork, you can continue using your existing fork to raise a new issue or make additional contributions. There is no need to fork the repository again.
@reshamsai150

[Sneha123-zudo]

@reshamsai150
You don't need to fork the repo again and again. Once you have forked it and clone it to your local then you don't have to fork it again .
Yeah , but you have to get updated your forked repo means as everyone contributing to that project so there must be some changes so you have to update it in your local.
You can do it by copying the code of main repo as you do during cloning. And command should be:-

1. git remote add upstream
2. git pull upstream main
3. git pull upstream main --rebase

By this you can update your fork.

[nishant05gaurav]

You can honestly use the present fork you have already got for raising the difficulty! There's no need to create a brand-new fork just for reporting trouble.

[nileshsn]

@reshamsai150

If you've already contributed to the repository and raised a new issue there, it's best to continue using your existing fork. This keeps your contributions centralized and makes it easier for maintainers to review your work in the context of your previous contributions.