Skip to content

foundry-cost-control v1.0.0b3 - Switch using new camelCase rule match properties - #10416

Draft
Darren Cohen (dargilco) wants to merge 5 commits into
Azure:mainfrom
dargilco:dargilco/switch-match-properties-to-camel-case
Draft

Darren Cohen (dargilco) wants to merge 5 commits into
Azure:mainfrom
dargilco:dargilco/switch-match-properties-to-camel-case

Conversation

@dargilco

@dargilco Darren Cohen (dargilco) commented Sep 30, 2026 •

Copy link
Copy Markdown
Member

This checklist is used to make sure that common guidelines for a pull request are followed.

Related command

General Guidelines

  • [YES] Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
  • [YES] Have you run python scripts/ci/test_index.py -q locally? (pip install azdev required)
  • [YES] My extension version conforms to the Extension version schema

For new extensions:

About Extension Publish

There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

@a0x1ab

Copy link
Copy Markdown
Member

/azp run

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
Successfully started running 2 pipeline(s).

@a0x1ab

Copy link
Copy Markdown
Member

/azp run

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
Successfully started running 2 pipeline(s).

@yonzhan

Copy link
Copy Markdown
Collaborator

foundry-cost-control

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.

4 participants