top button
Flag Notify
    Connect to us
      Facebook Login
      Site Registration Why to Join

Facebook Login
Site Registration
Print Preview

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

0 votes
32 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 Google+ Share Button LinkedIn Share Button Multiple Social Share Button

2 Answers

0 votes

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
0 votes

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 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

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?

0 votes

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

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?


Useful Links with Similar Problem
Contact Us
+91 9880187415
sales@queryhome.net
support@queryhome.net
#470/147, 3rd Floor, 5th Main,
HSR Layout Sector 7,
Bangalore - 560102,
Karnataka INDIA.
QUERY HOME
...