bitbucket - Cleaning up a mercurial repository for an external contractor -
i have active project sensitive files , directories. want hire external contractor simple ui work. however, don't want contractor have access directories , files. project in mercurial on bitbucket.
what best way clean project , give him access commit changes? thought forking new repository, worried removing directories don't want him have access to.
how remove them don't appear original changesets? how merge repo without removing directories in main repository? fork way go?
naturally repository needs access whole history in order self-check integrity. don't know of way selectively hide parts of repository (there's acl extension, write access only).
in case, would
- create new repository sensitive information has been stripped off (use convert extension task).
- then let external guy work repository.
- once work finsihed, pull repository clone of original 1 (using
-f
force pulling of unrelated repository), and - rebase first changeset , children onto head of original repository.
- finally, push rebased head original repository.
for steps 3 5 don't have wait until external developer done. rebasing intermediate states of repository possible.
yet, it's theoretical idea .. 1 has see how performs in practice.
alternative: in case have external contractors shouldn't see parts of code, second @anton's comment setup permission related multiple repositories.
Comments
Post a Comment