how to protect my source while allowing a new developer to work in Git

352 views

I've got a new developer who I'm concerned might hurt our git repository (by checking into master for example) if we give him r/w access to our bitbucket repo. I want him to be able to check in to his branch only and be able to merge master changes to his branch, but I don't want him to be able to commit to the master branch.

posted Jun 6, 2013 by anonymous

Share this question

Facebook Share Button

Twitter Share Button

LinkedIn Share Button

2 Answers

Git does not support branch permissions. The best way to deal with that kind of permissions-thingy is to create two repos : a main repo and a fork for your new developer. He would only have permissions to pull from the main repo but could do "pull-request" to the main repo. That way you could review his work
before merging it into the main one.

answer Jun 6, 2013 by anonymous

Git doesnt provide such thing by default. To achieve that, you should use external software, like gitosis or gitolite.

answer Jun 6, 2013 by anonymous

Similar Questions

+1 vote

I can't find my git.exe in android studio while using android studio version control?

I want to connect my android studio with git and installed git separately and when I enable version control. There is an error
"Cannot run program "git.exe" The system cannot find the file specified" searched in C drive programs files and X86 too but didn't get git.exe location.

+2 votes

How to add my local repository files to a server repository in Git

I have a local repository and want to change the master branch to a server git. (I just don't want to delete all files in repository and then clone the server files)How to do that? I guess I have to fetch server data into local directory, merge an push it. Can someone please explain me how to do?

+2 votes

Would it be possible to add -u option to git tag for updating tag (with message) to a new commit, e.g. after rebase

Ref
http://stackoverflow.com/questions/8044583/how-can-i-move-a-tag-on-a-git-branch-to-a-different-commit

0 votes

When I update a branch in GIT from master I don't get the same files as when I create a new branch?

When I update my branch from master it pulls down several files, including some sass files. When I compile, however, gulp alerts me that I am missing .scss files.

I tested this by creating a new fresh branch and running gulp sass. This time there were no errors and I saw the missing .scss had been brought in.

Would anyone know why, on update, I am only getting some of the files from master?

+2 votes

Creating a new branch in GIT

I would like to know what are the best practices when creating a new branch. For example. If I get a request to do update website title from XYZ to ABC; then should I create a branch named; "Update Title"? Or I should prefix this as suggested here (http://stackoverflow.com/questions/273695/git-branch-naming-best-practices). Are there any official prefixes?

Also I am concerned about the following; Let us say I create the branch named "Update Title". Finish the change. Merge back with Master. I then get another request to change title from ABC to DEF. Can I create another branch "Update Title". Will not this be confusing?

...