Skip to content

Instantly share code, notes, and snippets.

View cvega's full-sized avatar
🎛️
git commit -m '[FIXED] - *'

Casey Vega cvega

🎛️
git commit -m '[FIXED] - *'
  • GitHub Staff
  • San Francisco, CA
  • 10:13 (UTC -07:00)
  • LinkedIn in/caseyvega
View GitHub Profile
https://silentspacemarine.com/68716263a9b102719aa1c7cc606c6c84306c42bf317770227aa2e45d2e4d7231-12dbcc46
@cvega
cvega / 1-orgs-archetype.md
Created April 26, 2023 21:00 — forked from whatupfoo/1-orgs-archetype.md
Orgs and Teams Best Practices

Organization archetypes

The intention of this document is to provide some guidance and suggestions to customers who are wondering how they should structure organizations and teams in their GitHub Enterprise environment. The idea isn't to give hard and fast rules on which approach is better than the other, but to give examples of when one approach might be preferable to another depending on the use case.

1. A single organization with direct organization membership for repository access (not teams)

          ________________
          |     Org      |
          |    ______    |
          |   |      |\  |

| | Repo | \ |

[colors]
indexed_colors = []
[colors.bright]
black = "0x4d4d4d"
blue = "0xcaa9fa"
cyan = "0x9aedfe"
green = "0x5af78e"
magenta = "0xff92d0"
red = "0xff6e67"