Org-level labels config

blindnet-io / .github

Community health files for the @blindnet-io organization

1 stars 0 forks source link

Org-level labels config #4

Closed nweldev closed 2 years ago

nweldev commented 2 years ago

Add configuration for a first clean-up of labels in existing repos using https://github.com/Financial-Times/github-label-sync

See blindnet-io/devrel-management#12

nweldev commented 2 years ago

I updated the following repositories with this config:

clients-management
blindnet-docs
communication-management
devrel-management
staff-management

Other repositories require these labels to be discussed with @blindnet-io/engineering and updated accordingly to better-fit expectations and dev processes.

filipblnt commented 2 years ago

How about adding labels to distinguish the environment related to a product, e.g. production/staging? I think it is useful for issues directly related to product since it would allow to see more clearly where bugs happen and prioritise better.

nweldev commented 2 years ago

https://github.com/blindnet-io/.github/pull/4#issuecomment-1137115324 fixed in ddca2c5

nweldev commented 2 years ago

@filipblnt I applied these labels to product-management. Now you can do the same with code base repos whenever you see fit.

filipblnt commented 2 years ago

Actually you can apply it right away to all code repos since we don't have any custom labels defined in them anyway, there's no problem about that.