-
Notifications
You must be signed in to change notification settings - Fork 5.3k
Run OneLocBuild and SourceIndex on schedule instead of every commit in runtime-official.yml #123539
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
Merged
akoeplinger
merged 1 commit into
dotnet:main
from
akoeplinger:schedule-onelocbuild-sourceindex
Jan 23, 2026
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
The schedule definition is missing the
always:property. Based on the codebase conventions, all schedule definitions include this property to explicitly control whether the schedule runs unconditionally or only when there are changes since the last successful run.For localization and source indexing, you likely want
always: trueto ensure these tasks run on schedule regardless of code changes (since localization data and source indexing may need updates even without code changes). Alternatively, if you want to conserve resources by only running when there are code changes, usealways: falsewith a clarifying comment.