Karo Zans <karozans1...@gmail.com> writes:

My company currently has a structure where several teams work on the same project. Right now our current system has permissions built in that only allow you to make changes to certain files. Basically file permissions.

In GIT, is there a way to only allow certain teams/users to make
modifications to only the files they are allowed?

Is creating multiple repositories the only way to accomplish that?

Git doesn't really have any native support for that, but it can be
implemented through (rather complex) hook scripts (see
https://git-scm.com/docs/githooks). I believe some hosting solutions do offer such things, but don't take my word for it, do your own research.

I do want to point out though that often companies believe they want
access control, because that's what they are used to. In very many
situations it would work just as well with an immutable ledger and the ability to easily and quickly revert changes... and those things are
*very* well supported in Git :)

/M

--
Magnus Therning              OpenPGP: 0x927912051716CE39
email: mag...@therning.org   jabber: mag...@therning.org
twitter: magthe               http://therning.org/magnus

Only put off until tomorrow what you are willing to die having left
undone.
    — Pablo Picasso

--
You received this message because you are subscribed to the Google Groups "Git for 
human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Attachment: signature.asc
Description: PGP signature

Reply via email to