Skip to content
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

ICU-22873 Update CI to clang18 and enable -Werror #3134

Merged
merged 1 commit into from
Sep 19, 2024

Conversation

rp9-next
Copy link
Contributor

@rp9-next rp9-next commented Sep 6, 2024

Checklist
  • Required: Issue filed: https://unicode-org.atlassian.net/browse/ICU-22873
  • Required: The PR title must be prefixed with a JIRA Issue number.
  • Required: The PR description must include the link to the Jira Issue, for example by completing the URL in the first checklist item
  • Required: Each commit message must be prefixed with a JIRA Issue number.
  • Issue accepted (done by Technical Committee after discussion)
  • Tests included, if applicable
  • API docs and/or User Guide docs changed or added, if applicable

rp9-next added a commit to rp9-next/icu that referenced this pull request Sep 13, 2024
@jira-pull-request-webhook
Copy link

Hooray! The files in the branch are the same across the force-push. 😃

~ Your Friendly Jira-GitHub PR Checker Bot

@rp9-next rp9-next marked this pull request as ready for review September 13, 2024 08:30
@rp9-next rp9-next changed the title ICU-22873 Enable -Werror on clang16 CI ICU-22873 Update CI to clang18 and enable -Werror Sep 13, 2024
.github/workflows/icu4c.yml Show resolved Hide resolved
.github/workflows/icu4c.yml Outdated Show resolved Hide resolved
.github/workflows/icu4c.yml Outdated Show resolved Hide resolved
@jira-pull-request-webhook
Copy link

Notice: the branch changed across the force-push!

  • .github/workflows/icu4c.yml is different

View Diff Across Force-Push

~ Your Friendly Jira-GitHub PR Checker Bot

Copy link
Member

@roubert roubert left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@markusicu
Copy link
Member

Hi @rp9-next we normally let team members merge their own pull requests (partly in case they want to look it over themselves and maybe tweak something). Given our time zone difference, do you want us to merge some of your PRs on your behalf when they are approved? If so, maybe note that in the PR description? Or we try to remember which team member is generally ok with that?
@richgillam @echeran @mihnita opinion?

@rp9-next
Copy link
Contributor Author

Hi @rp9-next we normally let team members merge their own pull requests (partly in case they want to look it over themselves and maybe tweak something). Given our time zone difference, do you want us to merge some of your PRs on your behalf when they are approved? If so, maybe note that in the PR description? Or we try to remember which team member is generally ok with that? @richgillam @echeran @mihnita opinion?

Thanks, I am generally ok for people to merge my PRs (Due to time zone differences, I get time to amend any changes before anyone reviews). I will try to keep a message in description in the future, or perhaps a label (like "ready-to-merge" or "author-approves") ?

@rp9-next rp9-next merged commit 59d39a2 into unicode-org:main Sep 19, 2024
101 checks passed
@rp9-next rp9-next deleted the fix_Werror_for_clang16 branch September 19, 2024 06:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants