-
Notifications
You must be signed in to change notification settings - Fork 419
CLDR-18193 add Piemontese #4293
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
CLDR-18193 add Piemontese #4293
Conversation
|
We can merge from main to 48 too. |
5a4d6e8 to
49460a8
Compare
|
Notice: the branch changed across the force-push!
~ Your Friendly Jira-GitHub PR Checker Bot |
|
nothing had been merged to ddl/v48 yet but ddl/v48 is now up to date with main. So i moved the branch target to v48 |
srl295
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK except for the testData file being changed, just remove that
49460a8 to
38c041b
Compare
|
Hooray! The files in the branch are the same across the force-push. 😃 ~ Your Friendly Jira-GitHub PR Checker Bot |
38c041b to
bab1546
Compare
|
Notice: the branch changed across the force-push!
~ Your Friendly Jira-GitHub PR Checker Bot |
bab1546 to
3dc931e
Compare
|
Notice: the branch changed across the force-push!
~ Your Friendly Jira-GitHub PR Checker Bot |
3dc931e to
027c78e
Compare
|
Notice: the branch changed across the force-push!
~ Your Friendly Jira-GitHub PR Checker Bot |
dismissing prior changes requested because it has been fixed
CLDR-18193
Putting this up to merge into main -- but won't actually merge until the v47 cutoff, targetting v48. There are a lot of data updates on the main branch not in the v48 branch that I'd like to keep.
ALLOW_MANY_COMMITS=true