Adopt Fork-Based Workflow

[leseb]

Background:
The repository has too many branches, making it cluttered and difficult to manage / navigate.

Proposal:
Switch to a fork-based workflow where everyone forks the main repository, create branches in their forks, and submit pull requests (PRs) from there.

Next step if agreed:
Cleanup all inactive branches.

Looking forward to feedback!

[terrytangyuan]

+1

[nathan-weinberg]

+1

[booxter]

Yes please. It's a clutter and we have to pull all these private branches for no reason.

[jaideepr97]

+1

[booxter]

btw one other issue with using the main repo for private branches is that, apparently, Insights tab will include all these patches in contribution stats, e.g. see here: https://github.com/meta-llama/llama-stack/pulse/halfweekly

[ashwinb]

yes yes yes please

[nathan-weinberg]

Something like this could maybe help? https://github.com/marketplace/actions/remove-stale-branches

[booxter]

@nathan-weinberg it's probably helpful; but doesn't fix the problem though, no? I think the idea is for folks with push access to the repo to stop using the main repo for private branches (instead working in their github forks). (Over time, I think it could make sense to remove direct push access to the main repo for most of contributors; only leaving it as a safety hatch for emergencies in the hands of a selected few.)

[leseb]

Updates: Most of the stale branches have been cleaned up, and it looks like nearly everyone has adopted the workflow, so we’re almost at a resolution! :)