Skip to content

Instantly share code, notes, and snippets.

View davelacy's full-sized avatar

Dave Lacy davelacy

View GitHub Profile
@davelacy
davelacy / 1-orgs-archetype.md
Created December 15, 2022 20:08 — 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 | \ |

@davelacy
davelacy / unique-committers.sh
Last active October 20, 2022 19:07
Unique active committer count for non-GitHub customers
#! /usr/bin/env bash
# ***DISCLAIMER: Only tested on MacOS & Linux***
# Author: Dave Lacy (@davelacy)
# Created: 2022-05-17
# Updated: 2022-05-19
# Purpose: To provide a best guess estimate of the number of unique committers for GHAS pricing estimates. For organizations currently using 3rd party git version control products like ADO, GitLab, BitBucket, etc.
# Before use, make sure you:
0x5f8c604c486a4f51f570ad97a7b69b51f299f8b8
0x04013f0ee64d755945a1c3fd3819d0dba128c0af
0xC39e8a406DF1510928a7e5cECA848769f4521Ac4