The GitHub Provisioning Plugin synchronizes Registry data with GitHub. |
Registry CO Person Transaction | Changelog Action |
---|---|
Add | Add CO Person's group memberships to GitHub team memberships |
Edit | Synchronize CO Person's group memberships with GitHub team memberships |
Enter Grace Period | No changes (unless attributes change as part of grace period) |
Expiration / Becomes Inactive | Remove CO Person's group memberships from corresponding GitHub team memberships |
Unexpire / Becomes Active | Synchronize CO Person's group memberships with GitHub team memberships |
Delete | Remove CO Person's group memberships from corresponding GitHub team memberships |
Manual Provision | Synchronize CO Person's group memberships with GitHub team memberships |
Registry CO Group Transaction | Changelog Action |
---|---|
Add | Add CO Group's memberships to corresponding GitHub team |
Edit | Synchronize CO Group's memberships with corresponding GitHub team |
Delete | Remove CO Group's memberships from corresponding GitHub team |
Manual Provision | Write CO Group record (including memberships) to changelog |
In order to reduce the number of queries that count towards GitHub's API rate limit, the GitHub Provisioner uses a file based caching mechanism, with cache files written to This means that if multiple web servers are running COmanage Registry, each will have its own cache, effectively doubling the number of uncached queries. Under typical usage, this should not be a problem, though for heavier usage something like a database cache (CO-945) may be required. |
There are several ways to attach GitHub usernames to CO Person records. All require the extended identifier type GitHub to be created first.