preventing destructive operations to central repository
- From
Brendan Miller <catphive@catphive.net>
- Date
- Apr 16, 2010, 00:39 UTC
- Message-ID
- <j2yef38762f1004151739x497106eeo190b97f3eecc153f@mail.gmail.com>
Let's say you have a bare git repository writeable by a number of different people. How do you prevent them from borking the central repository?
Also, is there an automated mechanism to ensure that the timeline stays clean? Say, force people to rebase their repositories before merging into the shared repository?
Thanks