Bicep good first issues

25 open Bicep issues currently match the default 10+ star filter. Scored difficulty: 5,946 at 1/5, 8,786 at 2/5, 12,698 at 3/5, 12,117 at 4/5, 857 at 5/5. This hub uses the same feed as the homepage, limited to repositories whose GitHub language is Bicep.

All languages · Browse projects · How to find good first issues

Active projects

Unique repos with open help-wanted issues updated in the last 30 days

Showing 25 of ~25 matching filters (Bicep · 10+ stars)

List
Azure/bicep

Linter rule to detect referencing of child resources using `resourceId()` function

AI summary

This issue proposes a new linter rule for Bicep to detect and warn against the use of the `resourceId()` function to reference child resources, specifically subnets within virtual networks. The goal is to encourage a more idiomatic and maintainable approach using `existing` resources and direct property access for better readability and type safety.

enhancementgood first issuestory: linter rules
3.6K
Difficulty
3/5

Deploy all subnets as private subnets

AI summary

This enhancement request aims to configure all subnets within the project to be private. The issue is labeled as a 'good first issue', suggesting it's suitable for newcomers and likely involves straightforward configuration changes rather than complex architectural modifications.

enhancementgood first issuespokehub
17
Difficulty
2/5
Azure/bicep

Request for Feedback & Ideas on Bicep Best Practices

AI summary

The task is to contribute to a discussion on Bicep best practices by sharing personal experiences, identifying anti-patterns, suggesting improvements, and linking to helpful resources. This will help shape future Bicep tooling, documentation, and community standards.

documentationhelp wanted
3.6K
Difficulty
2/5

Github Copilot Metrics endpoint returning more than 28 days

AI summary

The task is to modify the GitHub Copilot Metrics Viewer application to handle cases where the GitHub Copilot Metrics API returns data beyond the expected 28-day window. The application currently displays data for the 'Last 28 days' but is showing more, leading to misleading information. The solution should make the application robust to changes in the API's date range, ensuring it only processes and displays the most recent 28 days of data regardless of what the API returns.

enhancementhelp wantedgood first issue
486
Difficulty
4/5

Also browsing: Python , TypeScript , JavaScript