[Tracking] GitVersion v7 release roadmap
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Idoneità per principianti
- 20/100
Direzione di ricerca
Inizia dalle issue principali collegate e dalle milestone 7.0.x e 7.1.x; questa issue è una roadmap più che un'attività di implementazione autonoma. Esamina i gruppi rimanenti e le relazioni di blocco, quindi conferma che ogni elemento sia completato, spostato a una milestone successiva oppure contrassegnato esplicitamente come opzionale o rinviato prima di decidere se il release è pronto.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Purpose
Track and order the remaining GitVersion v7 work across the 7.0.0, 7.0.x and 7.1.x delivery milestones. The 7.x umbrella milestone contains this roadmap, #2275 (New CLI), and #5031 (managed Git). Existing umbrella issues retain their own sub-issues; this roadmap links only their top-level parents plus standalone work. Umbrella milestone membership does not make all remaining umbrella work a v7.0 release gate; delivery scope is tracked by the release milestones and completion groups below.
The order below is the recommended delivery order. Explicit GitHub blocking relationships remain authoritative where present. Items within the same group may proceed in parallel when they do not share dependencies.
Current status — 2026-11-18
Updated by Codex on behalf of Artur (@arturcic).
Live issue-distribution snapshot checked 2026-11-18 07:45 CET: 16 open issues: 0 in 7.0.0 or 7.0.x, 11 in 7.1.x, 4 in 7.x (3 umbrella/tracking issues and #5267), and 1 in 8.x. No open issues are unmilestoned. Milestone totals below include both issues and PRs; this open-issue count excludes PRs.
- Stable 7.0.0 is published from
8fd9e294be12083242079edf2bf4dae4c0956164, the same source revision as beta.2. GA release CI passed on attempt 2. The release milestone is closed; all 145 expected GitReleaseManager entries are included in the published notes. - .NET 11 GA adoption and compatibility work is complete under #5394. #5490's Intel macOS restoration is implemented by merged #5491, published in beta.2 and stable 7.0.0, and validated by actual beta.2 installation/execution on an Intel macOS Azure agent. The stable parent tool package maps
osx-x64to the publicGitVersion.Tool.osx-x647.0.0 package; both macOS standalone archives were verified. - Open v7.x performance bug: #5267 — Slow branch-source discovery with many branches, area: Performance / Git history. Reproduction and profiling needed; no implementation PR or confirmed blocking dependency. This remains deferred outside the v7.0 completion gate.
- Under team review: #4433 via PR #5140.
- Scheduled for v7.1: #4057 and Mainline bug #5405 via open PR #5295. These fixes are not on
mainand must not be claimed as delivered in v7.0. - Draft implementation: #5040 via PR #5396, removing LibGit2Sharp and native Git payloads.
- Draft implementation: #3981 via PR #5391, blocked by #5040. #2921 and optional #5041 also depend on #5040. These remain v7.1 work.
- Distribution status rechecked: Homebrew 7.0.0 is merged and GitTools Actions v5.0.0 is public. winget #483008 and SchemaStore #6682 remain open for upstream review; submission is complete, upstream availability is pending.
- Completed delivery recorded below includes #5245/#5246, #4998/#5207, #5210/#5393, #5263/#5264 and #5253/#5259.
v7.0 release verification — updated 2026-11-18
The approved stable 7.0.0 release is published from 8fd9e294be12083242079edf2bf4dae4c0956164. Core publication and stable docs verification are complete. Homebrew 7.0.0 is merged and stable GitTools Actions v5.0.0 is published. The winget 7.0.0 manifest and SchemaStore 7.0 schema PRs have been submitted; both upstream merges remain pending. Coverage, Sonar and security observations below retain the evidence from the 2026-11-17 source-readiness audit; they do not claim a new analysis of later main commits.
| Area | Verified state |
|---|---|
| Source and release CI | Release-source workflows passed, including source CI and GA release CI, attempt 2: 85 successful jobs and two skipped jobs. Skipped jobs are not counted as passes. Stable docs were published separately after #5495 merged. |
| Coverage | Codecov project and patch statuses pass; project coverage is 85.10%. The earlier pending/failing snapshot is superseded. |
| SonarCloud | Main analysis records this exact revision and has an OK quality gate and zero unreviewed security hotspots. Seven previously documented maintainability findings remain: two static-local-function suggestions, four static-method suggestions, and one CSS-transition-properties suggestion. They remain separate existing backlog under the evidence recorded in #5394; this does not claim zero Sonar issues. |
| Security alerts | No open GitHub Dependabot or Code Scanning alerts at the readiness check. |
| Release milestone | The exact 7.0.0 milestone is closed with 0 open and 165 closed items (55 issues and 110 merged PRs). Its listing and milestone index agree. Every item has exactly one classification: 9 breaking changes, 27 features, 19 bugs, 14 improvements, 62 dependencies and 14 documentation entries (145 included); 20 build entries are intentionally excluded. No unmerged PRs, not-planned issues or duplicate PR/closing-issue pairs remain in the milestone. |
| Published 7.0.0 GA artifacts | All 11 exact-version NuGet packages are public, including all eight runtime tool packages. All eight standalone archives have verified SHA-256 digests and architectures, including both macOS architectures. All 13 version-qualified Docker Hub manifests contain AMD64 and ARM64 images; stable latest matches GA. GHCR publication succeeded with recorded digests, although anonymous registry inspection returned HTTP 401. Chocolatey 7.0.0 is approved and its package tests are passing. |
| Intel macOS | Actions #2287 merged after Azure build 13065 passed. Logs confirm .NET 11.0.100 osx-x64, installation of published beta.2 into darwin-x64, and successful tool execution. The macOS test job reports 221 passed and 25 skipped; skipped tests are not passes. Native-Intel beta.2 installation/execution remains the platform validation evidence. Stable 7.0.0 Intel package publication and the parent-package mapping have now also been verified; the stable-publication item in #5490 is checked. |
GA approval and coordination
- Refresh GitReleaseManager milestone inputs: #5480 — AngleSharp 1.10.4 and #5481 — coverlet.MTP 10.1.1 are assigned to
7.0.0; superseded AngleSharp #5471 was removed. The7.0.xumbrella is now empty. - Remove stale delivery entries: unmerged #2272 and #5063, abandoned fixture migration #5038, and superseded managed-default plan #5039. Actual v7.0 managed-default delivery remains represented by #5135. Only milestone membership changed; labels and closed states were retained.
- Coordinate stable GitTools Actions v5 availability. Stable v5.0.0 was published on 2026-11-18 at 05:25:59 UTC and is public, with draft and prerelease flags both false. The earlier pending-release snapshot is superseded. The GitVersion GA notification completed as a no-op because the configured
7.0.xrange already includes 7.0.0; Actions v5 publication is now independently verified. - Obtain explicit maintainer approval and publish final 7.0.0 using the existing release workflow. The stable release is public and the milestone is closed. GitReleaseManager-generated notes were repaired and reconciled to all 145 expected entries, with 20 build entries excluded; no missing or duplicate entries remain.
The earlier dependency-note consolidation intentionally omitted 131 intermediate/obsolete Dependabot entries; #5471 is now additionally superseded by #5480. Preserve this policy rather than re-adding intermediate entries through a generic missing-PR scan. Keep grouped PRs when they contain the latest change for any remaining component. The targeted #5480/#5481 refresh is complete. GitReleaseManager remains the source of generated GA notes; the published notes reconcile to 145 categorized entries and 20 build exclusions.
Post-publication verification and remaining distribution work
- Homebrew: publisher run succeeded on 2026-11-18. Homebrew PR #326269 is merged, including
depends_on "dotnet"and--output json. The earlier publishing-credential failure is superseded by this successful run; #5494 fixed the tap/formula lookup issue. - winget manifest submission: publisher run succeeded on 2026-11-18 and created winget PR #483008. The PR is open for upstream review; this confirms submission, not merged winget availability. The earlier invalid-token failure is superseded by this successful run.
- winget upstream merge and availability: PR #483008 remains open, with manual installation review pending. Submission and a successful publisher run do not mark this merge complete.
- Verify the GitTools Actions GA notification: run completed as a no-op because
7.0.xalready includes 7.0.0. Stable Actions v5.0.0 publication is now separately verified above. - Publish and verify stable 7.0 docs, migration links, and both output and configuration schemas. Merged #5495 fixes runtime-package input discovery. Docs publication and Pages deployment passed. Public docs and schemas return HTTP 200; the manifest identifies stable 7.0.0, net11.0 and exact GA source
8fd9e294be12083242079edf2bf4dae4c0956164. - SchemaStore submission: merged #5019 connects the publisher to successful docs publication. The docs publication run passed on 2026-11-18, including the SchemaStore job, and created SchemaStore PR #6682 as
gittools-botfromgittools-bot/schemastore. The PR adds schema 7.0, makes it the default and updates the wrapper reference while preserving older versions. The PR link is included in the 7.0.0 release notes. - SchemaStore upstream merge and catalog availability: PR #6682 remains open; PR creation does not mark upstream publication complete.
- Verify exact-version GA artifacts: all 11 NuGet/tool/MSBuild packages, all eight standalone archives, final multi-architecture Docker manifests and stable
latest, approved Chocolatey publication with passing package tests, all 145 expected GitReleaseManager note entries, and the linked GA announcement. This records verification of newly published GA artifacts, separately from beta.2 validation.
Bot-fork synchronization was completed for the Homebrew and winget publishing forks using ancestry-checked non-force pushes. These active upstream repositories continue accepting commits; refresh their state at the GA cut. Fork drift alone and local OAuth scope limitations are not proof that CI publishing credentials will fail. The successful 6.8.0 Homebrew run remains the prior stable publishing reference.
Post-GA CI maintenance: #5496 — update GitTools cicd to v6 merged on 2026-11-18. This is subsequent main-branch maintenance, not a change to the published 7.0.0 source revision.
Group 1 — Release foundations and compatibility
These establish the architecture, configuration contract, migration path, and feature-selector lifecycle needed by the rest of v7.
- #5031 — Managed Git implementation umbrella
- Core managed implementation is complete: #5042 — Git CLI writes and network operations established the mutating backend, and #5084 — fully managed Git backend landed the managed reader and parity coverage on
main. - Package-build CI now exercises managed Git through merged #5175.
- v7.0 defaults to managed Git, with
GITVERSION_GIT_BACKEND=libgit2retained as the temporary fallback; completed by merged #5189. - #5040 removes LibGit2Sharp in v7.1.
- #5041 is an optional v7.1 accelerator, blocked by #5040, and is not a release gate.
- Core managed implementation is complete: #5042 — Git CLI writes and network operations established the mutating backend, and #5084 — fully managed Git backend landed the managed reader and parity coverage on
- #5131 —
calculation/outputconfiguration umbrella- #5132 — Versioned configuration, merged in #5158.
- #5133 — Migration and legacy warnings, merged in #5159.
- #5134 — Schemas and migration guidance, merged in #5160.
- Configuration foundation complete. #5135 owns v7.0 defaults/selectors; #5188 owns v7.1 legacy parser/configuration runtime removal, outside the v7.0 release gate.
- #5130 — Regex-based branch and tag exclusions
- Completed by #5147 — support regex tag exclusions and #5148 — support regex branch exclusions.
- #5135 — v7.0 defaults and feature selectors
- Managed Git is the v7.0 default, with the temporary libgit2 fallback retained.
- The configuration foundation #5131 is closed as completed; its dependency link records the satisfied prerequisite.
- Align parser, configuration, and Git-backend defaults and selector behavior for v7.0.
- Complete effective-selection logging and the documentation sweep.
- Completed by #5189 — Default to v7 feature selections and standardize compatibility selectors, merged on 2026-09-08.
- v7.1 legacy parser/configuration runtime removal is tracked separately by #5188.
- Followed by the v8 cleanup in #5136.
The configuration foundation and v7.0 selector/default alignment are complete. Completed v7.0 delivery is recorded in Groups 2–5; remaining GA publication tasks are tracked in the readiness audit above. Legacy implementation removal remains in the v7.1 completion group below.
Group 2 — Platform and breaking-change work
Review these after the release foundations are stable; implementation can be parallelized where independent.
-
- #5398 — Composable calculate and output commands: CLI/output work scheduled in
7.1.x, under #2275. Add separate calculation and repository-independent output stages with a JSON pipeline; no implementation PR yet.
- #5398 — Composable calculate and output commands: CLI/output work scheduled in
-
#3041 — Separate
SemVerSourcefromCommitCountSource, completed by merged #5199 on 2026-09-17. -
#4998 — .NET 11 support: completed by merged PR #5207 on 2026-10-19.
-
#5210 — Evaluate .NET 11 SDK, runtime and BCL improvements: completed by merged PR #5393 on 2026-10-21. GA adoption remains in #5394 and NativeAOT in #3981/#5391.
-
#5394 — Complete .NET 11 GA adoption and compatibility validation: closed as completed; related merged delivery includes #5472, #5473, #5474 and #5476.
-
#5490 — Restore Intel macOS packages and standalone artifacts: implemented by merged #5491, published in beta.2, and verified by native Intel macOS installation/execution in Azure build 13065. Stable 7.0.0 Intel package publication and its parent-package mapping are verified; the stable-publication item in #5490 is checked.
-
#5208 — Modernize selected code using C# 12–14 features
- Completed by merged #5209 on 2026-09-15; includes selected C# 12–14 modernization and nullable-contract improvements.
-
#5219 — Azure Pipelines output variable naming: completed by merged #5227 — Replace dotted Azure Pipelines variable names in v7 on 2026-09-21.
Group 3 — Version-calculation behavior and API capabilities
Prioritize confirmed regressions before new behavior, then complete independent feature work.
-
#5405 — Mainline version falls back to 0.0.x when a merge-message branch still exists: calculation bug scheduled in
7.1.x; open PR #5295 also addresses #4057. -
#5267 — Avoid excessive branch-source discovery work: performance/Git-history bug tracked in
7.x, with no specific minor-release commitment and outside the v7.0 completion gate. Reproduce and profile currentmainwith both Git backends, preserving source-branch inheritance and local/remote reference semantics. Distinct from the tagged-history optimization in #5246; no confirmed blocking dependency. -
#5245 — Avoid repeated revision walks per version tag: completed by merged PR #5246 on 2026-10-05. Independent of LibGit2Sharp removal (#5040) and the optional commit-graph accelerator (#5041).
-
#4654 — Incorrect
assembly-informational-versionoutput- Resolved by merged #4977, whose tokenizer supports custom numeric formats such as
0000;;''. Closure verification on currentmainconfirmed correct zero/nonzero results through both YAML configuration and CLI overrides; no further implementation is required.
- Resolved by merged #4977, whose tokenizer supports custom numeric formats such as
-
#3149 — Develop version after creating a release branch
- Completed by #5192 — Track prerelease tags on unversioned release branches, merged on 2026-09-09. Develop can advance from eligible prerelease tags on release branches without a version in their names; versioned release names retain precedence.
-
#4433 — Prevent increment of merged branch in GitHub workflow: scheduled in
7.1.x, outside the v7.0 completion gate.- Implementation PR #5140 remains open and is under team review.
-
#4057 — Multiple mainline branches: scheduled in
7.1.x, outside the v7.0 completion gate; PR #5295 is open. -
#3954 — Consistent
GIT_BRANCHhandling, completed by merged #5217 on 2026-09-17. -
#5228 — Parse
next-versionwithout requiringtag-prefix, completed by merged #5248 on 2026-09-28. -
#3035 —
{Sha}and{ShortSha}in branch labels- Completed by #5191 — Support commit SHA placeholders in branch labels, merged on 2026-09-09. Labels can use the commit being versioned, including historical calculations; named regex captures retain precedence. Documentation and generated schema are updated.
Group 4 — User experience and documentation
-
#5426 — Privacy-preserving CLI usage telemetry: completed by merged PR #5376 on 2026-11-02; telemetry is disabled by default.
-
#5360 — Repository-independent configuration validation: completed by merged PR #5361 on 2026-10-15; supports configuration validation without version calculation or repository initialization.
-
#5300 — Align version-calculation documentation with v7: completed by merged PR #5299 on 2026-10-15.
-
#5263 — Export an OpenCLI-compliant command description with
--cli-schema: implementation delivered by merged PR #5264 on 2026-09-30, providing--cli-schemaOpenCLI export for the shipped v7 parser. The issue is closed as completed. -
#5253 — Query an individual effective configuration property: completed by merged PR #5259 on 2026-09-30. Provides read-only effective configuration lookup for scripts, available only with v7 configuration.
-
#5187 — Improve documentation navigation and version clarity
- Completed by merged #5185: clearer navigation, version-specific guides and API references, and a consistent accessible documentation experience. Also closes #4537 — Confusing documentation version links.
-
#3915 — Document TrunkBased flow: closed as completed.
-
#5224 — Reference links and documentation style enforcement: closed as completed.
Nested-configuration documentation is complete under #5134; the broader site experience is tracked separately in #5187. The init wizard (#3900) is scheduled for v7.1 and is outside the v7.0 release gate.
Group 5 — Release and CI infrastructure
-
#5367 — Named-mutex failures in concurrent Linux MSBuild projects: closed as not planned; no implementation completion is claimed and this is not a release gate.
-
#5220 — Evaluate MTP GitHub test annotations and job summaries: closed as completed; #5226 merged on 2026-09-22.
-
#5221 — Import .NET test coverage into SonarCloud analysis: closed as not planned; no implementation completion is claimed and this is not a release gate.
The optional CI follow-ups are resolved: #5220 is completed and #5221 is closed as not planned. Neither blocks v7.0.
v7.0 completion group
Completed delivery is recorded in the 7.0.0 release milestone, including #5135. The 7.0.x milestone remains available for subsequent patch work:
- #5131 — Configuration implementation, migration tooling, schemas, and guidance: #5132–#5134 are complete. Later legacy-runtime removal remains in the v7.1 group.
- #5031 / #5135 — Make managed Git the v7.0 default, retaining
GITVERSION_GIT_BACKEND=libgit2as the temporary fallback. - #5135 — Complete v7.0 parser/configuration selector alignment: default to the v7 parser and nested configuration, preserve the temporary v6 fallbacks, validate selector values, and reject the retired boolean parser variable with replacement guidance.
- #5135 — Complete effective-selection logging and migration documentation without contaminating machine-readable output.
- #5187 — Improve documentation navigation and version clarity, completed by #5185.
- Release/CI foundations: #5090 — Docker Hub OIDC and #5103 — Self-repository Actions syntax.
- #3149 — Track prerelease tags on unversioned release branches, completed by #5192.
- #3035 — Support commit SHA placeholders in branch labels, completed by #5191.
- #5208 — Complete the selected C# 12–14 modernization and nullable-contract extras, delivered by merged #5209.
- #5219 — Replace dotted Azure Pipelines output variable names, completed by merged #5227.
- #3041 — Separate semantic-version and commit-count sources, completed by merged #5199.
- #3954 — Consistent branch environment overrides, completed by merged #5217.
- #5224 — Reference links and documentation style enforcement: closed as completed.
- #5228 — Parse
next-versionwithout requiringtag-prefix, completed by merged #5248 on 2026-09-28. - Optional CI follow-ups resolved: #5220 — MTP reporting is completed; #5221 — SonarCloud coverage is closed as not planned.
- #5263 — OpenCLI command description export: implementation delivered by merged PR #5264 on 2026-09-30, providing
--cli-schemaOpenCLI export for the shipped v7 parser. The issue is closed as completed. - #5253 — Query an individual effective configuration property: completed by merged PR #5259 on 2026-09-30. Provides read-only effective configuration lookup for scripts, available only with v7 configuration.
- #5245 — Avoid repeated revision walks per version tag, completed by merged PR #5246 on 2026-10-05.
- #5300 — Align version-calculation documentation with v7: completed by merged PR #5299 on 2026-10-15.
- #5360 — Repository-independent configuration validation: completed by merged PR #5361 on 2026-10-15; supports configuration validation without version calculation or repository initialization.
- #4998 — Add .NET 11 support, completed by merged PR #5207 on 2026-10-19.
- #5210 — Evaluate .NET 11 SDK, runtime and BCL improvements: completed by merged PR #5393 on 2026-10-21. GA adoption remains in #5394 and NativeAOT in #3981/#5391.
- #5394 — Complete .NET 11 GA adoption and compatibility validation: closed as completed; related merged delivery includes #5472, #5473, #5474 and #5476.
- #5490 — Restore Intel macOS packages and standalone artifacts: implemented by merged #5491, published in beta.2, and verified by native Intel macOS installation/execution in Azure build 13065. Stable 7.0.0 Intel package publication and its parent-package mapping are verified; the stable-publication item in #5490 is checked.
- #5426 — Privacy-preserving CLI usage telemetry: completed by merged PR #5376 on 2026-11-02; telemetry is disabled by default.
- Resolve the scheduled
7.0.xwork in Groups 2–5: no open issues remain in the milestone. Release readiness and publication remain separate decisions.
LibGit2Sharp and legacy parser/configuration removal belong to v7.1; selector removal belongs to v8. The optional #5041 accelerator is not a v7.0 release gate.
v7.1 completion group
Tracked in the 7.1.x milestone:
-
#5405 — Mainline version falls back to 0.0.x when a merge-message branch still exists: calculation bug scheduled in
7.1.x; open PR #5295 also addresses #4057. -
#5398 — Composable calculate and output commands: CLI/output work scheduled in
7.1.x, under #2275. Add separate calculation and repository-independent output stages with a JSON pipeline; no implementation PR yet. -
#4433 — Prevent increment of merged branch in GitHub workflow: PR #5140 is under team review.
-
#4057 — Multiple mainline branches: deliver multiple-mainline support; scheduled for v7.1, with open PR #5295.
-
#5040 — Remove LibGit2Sharp and native binaries: implementation PR #5396 is open as a draft; prerequisite for #3981 and NativeAOT PR #5391.
-
#2921 — Remote-reference operation without local branch copies: scheduled for v7.1, blocked by #5040, when managed Git is the sole backend; outside the v7.0 release gate.
-
#3900 — Revamp the init wizard: scheduled for v7.1.
-
#3981 — Trimming and AOT support: blocked by #5040 (LibGit2Sharp removal). Implementation #5391 is a draft and must not merge until #5040 lands on main; then rebase and simplify around the sole managed backend. Native platform/distribution validation gaps remain separate gates. Separate from #5210 and the GA checklist #5394.
Explicitly non-blocking follow-up
- #5041 — Commit-graph acceleration is scheduled in the
7.1.xmilestone and blocked by #5040 (LibGit2Sharp removal). It remains optional and must not block v7. - #5136 — Remove feature-selector environment variables is the v8 follow-up in the
8.xmilestone.
Release-management rules
- Keep this roadmap and the #2275 and #5031 umbrellas on the
7.xmilestone. Assign release-specific delivery issues to7.0.0,7.0.x,7.1.x, or the appropriate later milestone. - Add new v7 work to the appropriate group and as a direct sub-issue unless it belongs under an existing umbrella.
- Do not duplicate grandchildren such as #5132–#5134 or #5040–#5041 as direct sub-issues here.
- Move explicitly scheduled v7.1 work to the
7.1.xmilestone while retaining its parent hierarchy. - Before releasing v7.0, every open item must be completed, moved to a later milestone, or explicitly marked optional/deferred.
- Lingua principale
- C#
- Stelle
- 3.1k
- Fork
- 661
- Merge medio
- 7h 4m
- PR unite (30g)
- 77
Preparare l'ambiente
Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di GitTools/GitVersion
-
[ISSUE]: Mainline: version on main falls back to 0.0.x when a branch named in a merge message still existsForse già presa @arturcic l’ha presa 39 giorni fa. Apertabug
Difficoltà 4/5 3-5 giorni Idoneità per principianti 35/100
GitTools/GitVersion#5405 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
feature
Difficoltà 5/5 Più di una settimana Idoneità per principianti 35/100
GitTools/GitVersion#5398 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
bug
Difficoltà 4/5 3-5 giorni Idoneità per principianti 48/100
GitTools/GitVersion#5267 · 2 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 5/5 Più di una settimana Idoneità per principianti 30/100
GitTools/GitVersion#5188 ·
I maintainer di solito rispondono entro 1 giorno
-
breaking change configuration
Difficoltà 5/5 Più di una settimana Idoneità per principianti 35/100
GitTools/GitVersion#5136 ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di GitTools/GitVersion
Issue simili
-
documentation
Difficoltà 2/5 1-3 ore Idoneità per principianti 85/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
-
area/backend type/bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
umbraco/Umbraco-CMS#24668 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
Pri3
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
MicrosoftDocs/windows-dev-docs#6205 ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
I maintainer di solito rispondono entro 1 giorno