-
Notifications
You must be signed in to change notification settings - Fork 387
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-18271 Update release page cldr-47.md #4329
Conversation
✨ deployed to https://99825033.cldr.pages.dev |
✨ deployed to https://67062c19.cldr.pages.dev |
✨ deployed to https://775e1f6a.cldr.pages.dev |
✨ deployed to https://2b251c8f.cldr.pages.dev |
We could go ahead and merge this, as discussed in the meeting. |
Am squashing because of bad commit statement. |
✨ deployed to https://9e70058a.cldr.pages.dev |
✨ deployed to https://276e4483.cldr.pages.dev |
@conradarcturus - Are there other changes to the supplemental changes that we should include? Feel free to make a commit against this branch before the TC meeting tomorrow if you have time. We'll have to squash this PR in order to pass validation when we're ready to update the release page following tomorrow's TC meeting. |
✨ deployed to https://21819750.cldr.pages.dev |
0db8ac2
to
a893cc3
Compare
Hooray! The files in the branch are the same across the force-push. 😃 ~ Your Friendly Jira-GitHub PR Checker Bot |
✨ deployed to https://15c336ba.cldr.pages.dev |
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.
I went ahead and squashed this since I still saw it failing due to a bad commit message.
I've made some more changes so if it looks good to you we should go ahead and merge it. Otherwise, I'm happy to re-review later tonight if you'd like to make more changes.
Squashed and deleted branch; we can follow up with other PRs |
CLDR-18271
ALLOW_MANY_COMMITS=true