Skip to content

Commit 07d1de8

Browse files
committed
update
1 parent 607239d commit 07d1de8

2 files changed

Lines changed: 3 additions & 6 deletions

File tree

articles/azure-resource-manager/bicep/file.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Bicep file structure and syntax
33
description: Understand how to use declarative syntax to understand the structure and properties of Bicep files.
44
ms.topic: article
55
ms.custom: devx-track-bicep
6-
ms.date: 01/29/2026
6+
ms.date: 01/30/2026
77
---
88

99
# Bicep file structure and syntax

articles/azure-resource-manager/bicep/linter.md

Lines changed: 2 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Use Bicep linter
33
description: Learn how to use Bicep linter.
44
ms.topic: how-to
55
ms.custom: devx-track-bicep
6-
ms.date: 01/16/2026
6+
ms.date: 01/30/2026
77
---
88

99
# Use Bicep linter
@@ -94,10 +94,7 @@ You can integrate these checks as a part of your CI/CD pipelines. You can use a
9494

9595
Sometimes a rule has false positives. For example, you might need to include a link to a blob storage directly without using the [environment()](./bicep-functions-deployment.md#environment) function.
9696

97-
98-
You can suppress Bicep linter rules by using `disable-next-line` and `disable-diagnostics`. See [Directives](./file.md#directives).
99-
100-
If you want to suppress a linter rule, change the level of the rule to `Off` in [bicepconfig.json](./bicep-config-linter.md). In the following example, the `no-deployments-resources` rule is suppressed:
97+
You can suppress Bicep linter rules by using `disable-next-line` and `disable-diagnostics`. See [Directives](./file.md#directives). If you want to suppress a linter rule, change the level of the rule to `Off` in [bicepconfig.json](./bicep-config-linter.md). In the following example, the `no-deployments-resources` rule is suppressed:
10198

10299
```json
103100
{

0 commit comments

Comments
 (0)