fudali

Or pipeline triggered by tag can also be supported ？ @f-f

I think it's not just production environments, what if we have multiple environments? Can values-*.yaml be supported?

> @fudali113 interesting idea, do you have any examples of charts that have other `values-*.yaml` files today? my use cases like with @rgazaryants > Would be great to be able...

yes, choose and not input. reduce error rate

> Thanks for your advice. Since current, the library does not support parsing and formatting with all user-defined custom number format expressions, so I think this feature should be added...

i think the NLP lib and map the build-in number format index and number format is two things； 1. the NLP lib support more format features; 2. numFmtId map support...

and in https://github.com/qax-os/excelize/blob/fb6ce60bd56f4ef80d9fda76dc8accb4bfdee4ff/cell.go#L1327 The changes are roughly as follows： ```golang func (f *File) formattedValue(s int, v string, raw bool) (string, error) { if raw { return v, nil } if...

So how do you make that distinction? Is there any documentation I can refer to? i don‘t find system info or lang in excel xml files；and i find https://learn.microsoft.com/en-us/dotnet/api/documentformat.openxml.spreadsheet.numberingformat?view=openxml-2.8.1 document...

like `styles.go` langNumFmt ?  So is it now possible to override the default `builtInNumFmt` using `langNumFmt` in your `formattedValue`? In that case? How to deal with numFmtId = 14?

I've implemented another locale-based design； https://github.com/qax-os/excelize/pull/1525 @xuri PTAL