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

Localized file check-in by OneLocBuild Task: Build definition ID 679: Build ID 2641463 #112495

Closed

Conversation

dotnet-bot
Copy link
Collaborator

This is the pull request automatically created by the OneLocBuild task in the build process to check-in localized files generated based upon translation source files (.lcl files) handed-back from the downstream localization pipeline. If there are issues in translations, visit https://aka.ms/icxLocBug and log bugs for fixes. The OneLocBuild wiki is https://aka.ms/onelocbuild and the localization process in general is documented at https://aka.ms/AllAboutLoc.

Copy link
Contributor

Tagging subscribers to this area: @dotnet/area-infrastructure-libraries
See info in area-owners.md if you want to be subscribed.

Copy link
Member

@carlossanlop carlossanlop left a comment

Choose a reason for hiding this comment

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

Another spurious loc PR, @ericstj but I now understand why.

This one is coming from Build definition ID 679 (dotnet-runtime-official) Build 2641463: https://dnceng.visualstudio.com/internal/_build/results?buildId=2641463&view=results

It was triggered by a release/8.0-staging PR merged on Feb 12 at 8:58 AM (3 hours ago): #112374

The builds seem to be behind.

The next PR that was merged after the one above was mine that flows from release/8.0 to release/8.0-staging the single change that wraps the loc yaml code with an if check for SourceBranch. Merged 10 minutes ago: #112467

I'd like to think that this if check will be enough to stop triggering these PRs coming from 8.0 builds.

@carlossanlop carlossanlop deleted the locfiles/876ce5ac-4003-4274-a175-497f4aec9e05 branch February 12, 2025 20:05
@github-actions github-actions bot locked and limited conversation to collaborators Mar 15, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants