Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The repo access rights on a DVCS is always linked to the all repo, not part of if, mainly because you clone <em>all</em> of it (<a href="https://stackoverflow.com/questions/4929688/how-to-shallow-clone-a-single-branch-in-git/4929819#4929819">shallow clone is hard</a>).</p> <p>That means <a href="https://github.com/sitaramc/gitolite" rel="nofollow noreferrer">gitolite</a> (I won't even mention gitosis which is obsolete) can establish restrictions on:</p> <ul> <li>accessing a all repo</li> <li>writing only certain branches (but you cannot limit read access to certain branch)</li> </ul> <p>But <strong>it cannot prevent a user to access parts of a repo</strong>.</p> <p>However, since <a href="http://sitaramc.github.com/gitolite/master-toc.html" rel="nofollow noreferrer">gitolite v3 or 'g3'</a> (April 17th, 2012), you can, with <a href="http://sitaramc.github.com/gitolite/vref.html" rel="nofollow noreferrer">VREF rules</a>, prevent <a href="http://sitaramc.github.com/gitolite/vref.html#NAME" rel="nofollow noreferrer"><strong>writing (pushing to) certain <em>directories</em></strong></a> (in addition of certain branches).</p> <hr> <p>Original answer (<a href="http://sitaramc.github.com/gitolite/g2/master-toc.html" rel="nofollow noreferrer">gitolite V2 or 'g2'</a>, November 2011)</p> <p>See <a href="http://sitaramc.github.com/gitolite/g2/exbac.html" rel="nofollow noreferrer"><code>gitolite.conf</code> -- by example</a> and <a href="http://sitaramc.github.com/gitolite/g2/rpr_.html" rel="nofollow noreferrer">side note: "R" permissions for refs</a></p> <pre><code>repo gitolite-admin RW+ = sitaram # this is equivalent to: RW+ refs/.* = sitaram </code></pre> <blockquote> <p>Sitaram is the only admin. He can push, create, delete, or rewind any branch or tag in the gitolite-admin repo.</p> </blockquote> <pre><code> R master = wally # MEANINGLESS! WILL NOT DO WHAT YOU THINK IT DOES! </code></pre> <blockquote> <p>This won't work.<br> <strong>You can only restrict "read" access at the repo level, not at the branch level</strong>.<br> This is a git issue, not a gitolite issue. Go bother them, or switch to gerrit.</p> </blockquote>
    singulars
    1. This table or related slice is empty.
    1. POgitolite or gitosis: permission on directory inside of the repository
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USVonC
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COGiven gerrit is also based on git this shows it's actually possible to work around the issue.
      singulars
      1. PO
      1. USJan Hudec
    2. CO@JanHudec - quoting from Gitolite... "Meanwhile, people who desperately need this are directed to gerrit, which can do this because they have their own git stack and dont use the one written by Linus and currently maintained by Junio. With the native git stack, the best solution is to create a second repo and use that for the more "secret" branches. "
      singulars
      1. PO
      1. USAsh
    3. COYou are right about the read access. It can be given at repo level only but write access can be controlled at branch and tag levels
      singulars
      1. PO
      1. USAsh
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload