Skip to content

V0.3.4/housekeeping#8

Merged
gimlichael merged 2 commits intomainfrom
v0.3.4/housekeeping
Apr 24, 2026
Merged

V0.3.4/housekeeping#8
gimlichael merged 2 commits intomainfrom
v0.3.4/housekeeping

Conversation

@gimlichael
Copy link
Copy Markdown
Member

This pull request introduces a patch release (v0.3.4) focused on improving the default .gitignore templates for the .NET application and library scaffolds. The main goal is to ensure that newly generated solutions start with more comprehensive and standardized exclusions for common build, IDE, test, and workspace artifacts.

Key changes in this release:

.gitignore Template Improvements:

  • Expanded the shared .gitignore files in both dotnet-new-app-slnx and dotnet-new-lib-slnx scaffolds to ignore standard .NET build outputs (bin/, obj/), IDE state files (Visual Studio .vs/, Rider .idea/, user settings), test results, NuGet packages, publish output, BenchmarkDotNet artifacts, and common OS files. This helps keep repositories clean and free from local or transient files by default. [1] [2]

Changelog and Release Management:

  • Added a new v0.3.4 release entry in CHANGELOG.md summarizing the above improvements.
  • Updated changelog compare links to reference the new v0.3.4 tag.

Add the standard .NET, IDE, test, publish, and bot workspace exclusions to the shared scaffold templates so new app and library solutions start from cleaner defaults.
Record the scaffold .gitignore cleanup as the 0.3.4 patch release and keep the compare links aligned with the new entry.
@gimlichael gimlichael self-assigned this Apr 24, 2026
@gimlichael gimlichael merged commit 10416e0 into main Apr 24, 2026
1 check passed
@gimlichael gimlichael deleted the v0.3.4/housekeeping branch April 24, 2026 14:41
@greptile-apps
Copy link
Copy Markdown

greptile-apps Bot commented Apr 24, 2026

Greptile Summary

This housekeeping patch expands the shared .gitignore templates in both the dotnet-new-app-slnx and dotnet-new-lib-slnx scaffolds from minimal stubs into comprehensive, standard .NET exclusion lists, and records the change in CHANGELOG.md as v0.3.4. The two templates diverge correctly — the library template retains its existing *.snk (strong-name key) rule and adds DocFX _site/ output, while the app template omits both, consistent with the respective scaffold purposes described in their AGENTS.md files.

Confidence Score: 5/5

Safe to merge — changes are additive template improvements with no logic or runtime impact.

All three changed files contain only documentation/template content (gitignore patterns and a changelog entry). No P0 or P1 findings were identified. The gitignore patterns are standard, well-categorised, and the intentional differences between the app and lib templates are justified by their respective scaffold purposes.

No files require special attention.

Important Files Changed

Filename Overview
CHANGELOG.md Adds v0.3.4 entry dated 2026-04-24 and updates compare links correctly; no issues.
skills/dotnet-new-app-slnx/assets/shared/.gitignore Expands from a minimal 2-rule file to a comprehensive .NET gitignore covering build outputs, IDE state, NuGet, test results, publish, BenchmarkDotNet, and OS files; well-structured and correct.
skills/dotnet-new-lib-slnx/assets/shared/.gitignore Same expansion as the app template, plus retains the lib-specific *.snk rule and adds DocFX _site/ exclusion; appropriate differences for the library scaffold.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[User invokes scaffold skill] --> B{App or Library?}
    B -- dotnet-new-app-slnx --> C[Read app assets/shared/]
    B -- dotnet-new-lib-slnx --> D[Read lib assets/shared/]
    C --> E[Copy .gitignore\nbin/ obj/ .vs/ .idea/\nNuGet test results OS files\n.bot workspace]
    D --> F[Copy .gitignore\n*.snk + bin/ obj/ .vs/ .idea/\nNuGet test results DocFX _site/\nOS files .bot workspace]
    E --> G[Generated solution root]
    F --> G
    G --> H[Clean repo — no build/IDE/test artifacts committed]
Loading

Reviews (1): Last reviewed commit: "💬 update 0.3.4 changelog" | Re-trigger Greptile

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.

2 participants