One solution is to coordinate who 'owns' master, mutex style, using something like an intranet wiki.
When you 'hold the lock', you get to rebase and push, and 'release the lock', and if you've any sense the system will automatically ensure you haven't broken the build.
Of course, it's important not to waste time, as this serializes the commit process, as it were.
When you 'hold the lock', you get to rebase and push, and 'release the lock', and if you've any sense the system will automatically ensure you haven't broken the build.
Of course, it's important not to waste time, as this serializes the commit process, as it were.