Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Org-level labels config #4

Merged
merged 3 commits into from
May 25, 2022
Merged

Org-level labels config #4

merged 3 commits into from
May 25, 2022

Conversation

nweldev
Copy link

@nweldev nweldev commented May 24, 2022

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 nweldev self-assigned this May 24, 2022
@nweldev nweldev changed the title Org-level repo configuration Org-level labels config May 24, 2022
@nweldev nweldev requested a review from filipblnt May 24, 2022 22:04
@nweldev
Copy link
Author

nweldev commented May 24, 2022

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.

@nweldev nweldev marked this pull request as ready for review May 24, 2022 22:07
@filipblnt
Copy link
Member

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
Copy link
Author

nweldev commented May 25, 2022

#4 (comment) fixed in ddca2c5

@nweldev nweldev requested a review from filipblnt May 25, 2022 11:53
@filipblnt filipblnt merged commit 79b3c5a into main May 25, 2022
@nweldev
Copy link
Author

nweldev commented May 25, 2022

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

@filipblnt
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants