Provide ability to configure default labels
See original GitHub issueDetailed Description
To remove the hard coded nature of the current implementation.
Context
Right now, the set of default labels that are used when executing the label
command are hard coded into GRM. The values that were chosen were the ones that I use personally, but this isn’t ideal. We need to provide the ability to configure what default labels are created when running the label
command.
Possible Implementation
The default labels should be part of the configuration that can be added to the YAML file.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:2
- Comments:9 (8 by maintainers)
Top Results From Across the Web
Configure a default sensitivity label for a SharePoint ...
Configure a default sensitivity label for a SharePoint document library for new and unlabeled documents.
Read more >Use sensitivity labels to configure the default sharing link type
Use sensitivity labels to configure the default sharing link type for sites and documents in SharePoint and OneDrive.
Read more >Set default label values for files in Google Drive
With automated classification, label admins can construct rules that add labels when files are created or when file ownership is transferred.
Read more >Allow me to create a default set of labels for my repos #281
E.g. docs should be a default label IMO. update in 2019. closed Ability to set default issue labels per organization (colors and names)...
Read more >Default Sensitivity Labels Apply More Widely in SharePoint
Another change that's coming soon is the ability to configure a default sensitivity label for a document library, much like you can do...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I would say only
As these are the current defaults created by GRM: https://github.com/GitTools/GitReleaseManager/blob/develop/Source/GitReleaseManager/GitHubProvider.cs#L348-L356
Anything additional would be part of a new enhancement request. But as I said, that is just my opinion, and it would be up to @gep13 whether to include them under the same request or not.
🎉 This issue has been resolved in version 0.12.0 🎉
The release is available on:
Your GitReleaseManager bot 📦🚀