¶ Github Organization Setup
While reviewing our development process we have decided to review our github organization set up to ease up repository creation and make sure they are created in a homogeneous way.
¶ Organizational Settings
NOTE: Only modified setting will be listed here
¶ Member Permissions
¶ Base permission
By default members should have a write permission on repository
¶ Repository creation
Should be unchecked since they will be given using github teams
¶ Repository forking
Members should be allowed forking of private repository
¶ Actions
Enable local & third party Actions for this organization should be check to allow user to use github actions
¶ Admin repository permission
¶ Repository visibility changes
We should allow repository visibility changes by admin
¶ Repository deletion and transfer
We should allow repository deletion and transfer only for admin
¶ Repository Labels
To simplify the development process we have created an organization wide github label standard.
Those label will apply automatically to newly created repos.
Here are the existing label :
¶ Usage
Here are tables explaining usage of each label splited by priority, type and status
| Priority | Usage |
|---|---|
| Critical | Use when bug/enhancement/feature or bug is required for current or next pool test |
| High | Use when bug/enhancement/feature is important but not breaking change for current/next pool test |
| Medium | Use when bug/enhancement/feature must be done in a near future |
| Low | Use when bug/enhancement/feature can be process later on when their is time |
| To Determine | Use when priority need to be determined later on |
| Type | Description |
|---|---|
| Bug | Current issue is a bug |
| Feature | Current issue is a new feature |
| Enhancement | Current issue is an enhancement of an existing feature |
| Proof of concept | Current issue is a proof of concept |
| Status | Description |
|---|---|
| Blocked | Current issue is blocked |
| Abandonned | Issue has been adandonned |