Skip to content
Open
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs-mslearn/toolkit/changelog.md
Original file line number Diff line number Diff line change
Expand Up @@ -45,9 +45,9 @@ The following section lists features and enhancements that are currently in deve
### [PowerShell module](powershell/powershell-commands.md) v14

- **Added**
- Added `-WhatIf` support for resource provider registration in [New-FinOpsCostExport](powershell/cost-management/New-FinOpsCostExport.md).
- Added `-WhatIf` support for resource provider registration in [New-FinOpsCostExport](powershell/cost/new-finopscostexport.md).
- **Fixed**
- Fixed inverted verbose logging in [Start-FinOpsCostExport](powershell/cost-management/Start-FinOpsCostExport.md) that showed blank dates when a date range was specified.
- Fixed inverted verbose logging in [Start-FinOpsCostExport](powershell/cost/start-finopscostexport.md) that showed blank dates when a date range was specified.
- Addressed minor lint warnings across PowerShell commands.

<br><a name="latest"></a>
Expand Down
2 changes: 1 addition & 1 deletion docs-wiki/Home.md
Original file line number Diff line number Diff line change
Expand Up @@ -168,7 +168,7 @@ Please do the following before submitting a pull request:

4. Only address 1 issue per pull request and [link the issue in the pull request](https://github.com/blog/957-introducing-issue-mentions).
5. Be sure to follow our [coding guidelines](./Coding-guidelines.md) and keep code changes as small as possible.
6. Validate changes by running locally and running [[unit tests]].
6. Validate changes by running locally and running [[unit tests|Build and test]].
7. Enable the checkbox to [allow maintainer edits](https://docs.github.com/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork) so the branch can be updated for a merge.
8. Do all of the above before publishing your PR. You are welcome to create a draft PR to share and discuss ideas, but only publish when all code is committed, tested, and ready for review.
9. If you are working with others (especially internal teams), have 2 of your peers review your PRs. This will ensure a quicker turnaround as it is more likely that issues will be addressed before we review the PR.
Expand Down
73 changes: 0 additions & 73 deletions docs/_docs/services/compute/vritual-machines.md

This file was deleted.

Loading