CLDR-16346 Followup to PR 2731

[macchiati]

CLDR-16346

• This PR completes the ticket.

ALLOW_MANY_COMMITS=true
DISABLE_JIRA_ISSUE_MATCH=true

[srl295]

should use CldrUtililty.getCopyrightString("#") - maybe next time

[macchiati]

I can't check in because of a bad commit message, and the usual "Details" fix doesn't work:

NOTICE: Your previous squash attempt failed with code 422. If you get this error repeatedly, you may not have permission to push to this repository.`

[srl295]

I can't check in because of a bad commit message, and the usual "Details" fix doesn't work:

NOTICE: Your previous squash attempt failed with code 422. If you get this error repeatedly, you may not have permission to push to this repository.`

FYI @sffc what is this ?

Ok. You can disable the check. I'll dig out the info.

[srl295]

Hmm. It didn't disable the validation message.

I get 404 trying to squash, can you try again?

[srl295]

[X] Maintainers are allowed to edit this pull request.
If checked, users with write access to unicode-org/cldr can add new commits to your … branch. You can always change this setting later.

It looks like I'm NOT allowed to force push to your branch even though you checked this.

[macchiati]

Still fails: You are about to OVERWRITE the CLDR-16346-Followup-to-PR-#2731 branch in macchiati/cldr <https://github.com/macchiati/cldr>. Yes, I understand. This is what I want. NOTICE: Your previous squash attempt failed with code 422. If you get this error repeatedly, you may not have permission to push to this repository.

…

On Mon, Feb 27, 2023 at 9:15 AM Steven R. Loomis ***@***.***> wrote: [X] Maintainers are allowed to edit this pull request. *If checked, users with write access to unicode-org/cldr can add new commits to your … branch. You can always change this setting later.* It looks like I'm NOT allowed to force push to your branch even though you checked this. — Reply to this email directly, view it on GitHub <#2743 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACJLEMFW4J5DPP3GZUOTI4TWZTOKNANCNFSM6AAAAAAVE5N55E> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[srl295]

@macchiati can you try it again now that i took the # out of the PR title

[srl295]

unicode-org/jira-github-pr-check#28 referenced a 422 error when there was an emoji in the title

[srl295]

CLDR-16346 had the title BRS v43 in Resolution+, Mark

I dropped the +, - @macchiati can you try the squash again?

[macchiati]

That didn't help. sigh

…

On Mon, Feb 27, 2023 at 10:15 AM Steven R. Loomis ***@***.***> wrote: unicode-org/jira-github-pr-check#28 <unicode-org/jira-github-pr-check#28> referenced a 422 error when there was an emoji in the title — Reply to this email directly, view it on GitHub <#2743 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACJLEMAWDX44ZYX7KSBXEV3WZTVMFANCNFSM6AAAAAAVE5N55E> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[srl295]

I see that commit f2e0fe9 was updated correctly too.

@macchiati maybe after the TC call i can help you manually squash?

[macchiati]

sounds good!

…

On Mon, Feb 27, 2023 at 10:23 AM Steven R. Loomis ***@***.***> wrote: I see that commit f2e0fe9 <f2e0fe9> was updated correctly too. @macchiati <https://github.com/macchiati> maybe after the TC call i can help you manually squash? — Reply to this email directly, view it on GitHub <#2743 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACJLEMAMIPOIVQDNMUWGLLTWZTWJHANCNFSM6AAAAAAVE5N55E> . You are receiving this because you were mentioned.Message ID: ***@***.***>

The base branch was changed.