Fork a repository

I forked the repo owned by arnav-dev that we need for the integration tests. Send the newly created fork to Lina and Marco and ask them to confirm they can push branches and open pull requests from it by Friday; if either cannot, give them instructions to grant my account write access to their fork and pause test work until confirmed.

Before I hand this fork to the team, make it obvious which branch is the working copy, surface any open issues or PRs carried over from the original repo, and flag any large files over 10 MB that will break CI. Create a short checklist for Lina to follow when she first clones so she can verify remotes and push rights without asking me.

I forked arnav-dev/analytics and my clone only has main. Lina needs feature branches and to push CI changes, but I don't know if the original had named branches or if I missed an option. Tell me the likely cause and the exact steps I should run locally and on the web UI so Lina can see and use the same branches, plus what to say to her if branches still don't appear.

In the last three forks I created for open-source contributors, the work stalls because they can't push branches or CI fails. Where am I losing time or trust? Recommend one habit change I can adopt when forking (what checks to run, how to name the fork, and an onboarding message to paste in issue or PR) so collaborators can start work immediately.