This is an F# Template for:
net6.0
net6.0
This takes away the ambiguity that developers face when creating an OSS project. Such as:
GitRelease
build step commits latest CHANGELOG.md in the body and creates a git tag.
CHANGELOG.md
it will update that Pull Request with the version it was released in.GitHubRelease
build step publishes a GitHub Release via the CHANGELOG.md and adds any artifacts (nuget/zip/targz/etc).net6.0
- Target Frameworks
net6.0
.NET 6.0 installedCHANGELOG.md
CHANGELOG.md
net6.0
application - Target Frameworks
net6.0
win-x64
, osx-x64
and linux-x64
- Runtime Identifiers. Bundles the application via dotnet-packaging
win-x64
application in a .zip file.osx-x64
application in a .tar.gz file.linux-x64
application in a .tar.gz file.dotnet new install "MiniScaffold::*"
Then choose:
dotnet new mini-scaffold -n MyCoolNewLib --githubUsername MyGithubUsername
dotnet new mini-scaffold -n MyCoolNewApp --githubUsername MyGithubUsername -ou console
The scaffold defaults to using the main
branch for releases. If you release from a different branch, you can use the --releaseBranch <branch name>
parameter to use your release branch instead of the default.
GitHub Actions |
---|
Stable | Prerelease |
---|---|
This is used to automatically configure author information in the NuGet package, as well as configure push urls for repo locations.
Defaults to Library
When set to either Console or Library project and the supporting infrastructure around their respective types.
-bash: ./build.sh: Permission denied
This is because dotnet template loses permissions of files. (https://github.com/TheAngryByrd/MiniScaffold/pull/37) added a post hook to address this but this only fixes it for dotnet sdk 2.x users. dotnet sdk 1.x will need to run chmod +x ./build.sh
Appveyor's conventions around generating URLs based on the project name has some nuances. See this issue for details.