Skip to content

feat(lockless rendering): prepare for azldev updates to allow lockless rendering - #20006

Open
Dan Streetman (ddstreetmicrosoft) wants to merge 2 commits into
4.0from
ddstreet/lockless-prep
Open

Dan Streetman (ddstreetmicrosoft) wants to merge 2 commits into
4.0from
ddstreet/lockless-prep

Conversation

@ddstreetmicrosoft

Copy link
Copy Markdown
Contributor

Add 2 no-op commits in preparation of adding azldev support for lockless rendering.

Copilot AI balanced review requested due to automatic review settings November 5, 2026 21:35

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

🟢 Approval recommended

No active review issues are recorded for the configuration include and placeholder changes.

No open issues 🎉

What changed in this PR

Prepares the base project for upcoming azldev support for lockless rendering without implementing that support yet.

Changes:

  • Adds upstream-commits/*.toml to the base project's configuration includes.
  • Adds an empty lockless-components.txt placeholder.
File Description
lockless-components.txt Adds an empty placeholder for lockless-rendering preparation.
base/​project.toml Includes upstream-commit TOML files in the base configuration.

Review effort: Balanced

Comment thread base/project.toml
#

includes = ["comps/components.toml", "images/images.toml", "images/images.tests.toml"]
includes = ["upstream-commits/*.toml", "comps/components.toml", "images/images.toml", "images/images.tests.toml"]

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

question(blocking): I don't see that we have an upstream-commits folder. Just confirming that that includes can handle non-existent files and directories?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

as far as i can tell it does, running update and render works fine.

@ddstreetmicrosoft

Copy link
Copy Markdown
Contributor Author

/azp run

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
2 pipeline(s) were filtered out due to trigger conditions.

…l files

work on azldev to transition off using 'lock' files involves moving
component upstream commit configuration into separate toml files,
which need to be included during toml parsing.

this adds a directive to include those files using a glob
pattern. since there are currently no matching toml files, this is
currently a no-op.
work on azldev to remove use of 'lock' files will transition
individual components from using a 'lock' file to 'lockless'
rendering. as this is strictly a transitional process, a temporary
file named 'lockless-components.txt' at the same level as the
'azldev.toml' file will be used to record which components should use
'lockless' rendering; any not in the file will continue to use 'lock'
file rendering.

as this file currently contains nothing, this is currently a
no-op. after all components are transitioned to 'lockless' rendering,
and azldev is updated to remove support for 'lock' files, this file
will no longer be needed and should be removed.
@ddstreetmicrosoft

Copy link
Copy Markdown
Contributor Author

no-change force push to correct my commit subject that was using feature: instead of feat:...and i'm still not convinced that level of pedantry is really a helpful PR check.

@ddstreetmicrosoft

Copy link
Copy Markdown
Contributor Author

/azp run

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
2 pipeline(s) were filtered out due to trigger conditions.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants