Repository navigation
Restarted the Project With Modern .NET - #15
Conversation
This is a complete rewrite of the command line parser in modern C# and .NET 10. This will not only be a command line parser, but a CLI application framework that mirrors how ASP.NET Core works. For this reason the project was renamed to CLI.NET Core. This commit only scaffolds the rough repository layout, consisting of a read me, a license, a list of contributors, a changelog, docs, design materials, the source code, and tests. All old files that are no longer needed were deleted. Since the permissive MIT license has recently been used more and more by large corporations to take from the open source community and not give anything back, the license of this project was changed from MIT to LGPL 3.0. The LGPL still allows people to freely use the library in their own software, even for commercial projects, but making any changes to it forces the derivative work to be released under the same license, thus forcing companies to give back to the community.
The project now uses a set of linters and a code formatter to (1) find and correct problems in the code and (2) to consistently format all files. If you use Visual Studio Code to work on the project, all linters and the code formatter are configured to directly work in the code editor. A set of recommended extensions is included for the linters and the code formatter. The following tools are being used: - **CSpell**, a spell checker for code, to ensure that there are no misspellings in the code. - **MarkdownLint**, a linter for Markdown files, which ensures that the Markdown files are consistently formatted and standards are enforced. - **dprint**, an unopinionated, configurable code formatter with plugins for many languages. This code formatter is used to format Markdown, JSON, YAML, and TOML files in the project.
A new GitHub Actions Workflow was added, which runs the linters and the code formatter on every push to any branch.
Added two C# projects, one for the CLI.NET Core library and one for the sample app. Also added a solution in the new SLNX format that contains the two project. The projects are fully configured and have a custom read me.
lecode-official
added
Type: CI/CD
A completely new, modern logo was designed using Claude Design. It heavily borrows from the ASP.NET Core logo, with the "C" mark and a dot. The logo is available in both light and dark mode variants in the `design/` directory and a design guide for it was created.
088995a to
061f68b
Compare
09e3a85 to
de74e57
Compare
History Rewrite: Added AI Co-Authorship DisclosureThe five commits merged by this PR have been rewritten to disclose the use of AI assistance and to correct the author email address. No file content changed. The rewritten commits have byte-identical trees and unchanged author dates — only commit metadata (author email, commit message, and therefore the commit hashes) differs. Because this PR is already merged, GitHub still displays the original hashes above. Here is the mapping to the commits now on
Why the RewriteThis project is open source, and I want the use of AI in it to be transparent and verifiable. Three of the five commits were partially or fully produced with Claude, but the commit metadata did not reflect that:
These three commits now carry a Separately, all five commits had been authored with an auto-generated local email address ( VerificationThe original commits remain accessible through this PR's head ref, so anyone can confirm that only metadata changed: git fetch origin refs/pull/15/head:pr-15-original
git range-diff de74e57..pr-15-original de74e57..origin/development
git diff pr-15-original origin/development # empty output == identical contentGoing ForwardAI-assisted commits in this repository will carry the Rewriting published history is normally something to avoid. It was safe in this case: I am the sole developer on this repository, none of these commits had been merged into |
1 participant
Completely removed the old repository content and created a new setup including:
Closes issue #14.