jamesshenry

$repoRoot = Resolve-Path "$PSScriptRoot/.."

Write-Host $repoRoot

$sourceDirectory = Join-Path $repoRoot 'src'
Write-Host $sourceDirectory

$outputFile = "$repoRoot/.github/instructions/codebase.txt"
Write-Host $outputFile

jamesshenry

{
  "license": "MIT",
  "url": "https://github.com/lukeyou05/tacky-borders/releases/download/v1.3.1/tacky-borders-v1.3.1.zip",
  "hash": "6DA529D21C0DC4EB6F07D6D253951A21637812C7F61E80686AEB9530613A78AD",
  "bin": "tacky-borders.exe",
  "version": "1.3.1",
  "homepage": "https://github.com/lukeyou05/tacky-borders"
}

jamesshenry

Project Ideas

Ok. I'm going to list off some ideas for projects. You will have to determine if any particular idea is good enough to include in a portfolio. These aren't creative ideas. They likely already exist. Some are way too advanced while others are simplistic.

I will recommend to post any project you make to github and make a github project page for it. Explain in as much detail as possible how you made it, how it can be improved etc. Document it.

If you pick an advanced idea, setup a development roadmap and follow it. This will show some project management skills.

Another piece of advice for those who are design challenged. Use different front end frameworks and use different themes for those frameworks to provide appealing designs without looking like yet another bootstrap site.

jamesshenry

Project Ideas

Ok. I'm going to list off some ideas for projects. You will have to determine if any particular idea is good enough to include in a portfolio. These aren't creative ideas. They likely already exist. Some are way too advanced while others are simplistic.

I will recommend to post any project you make to github and make a github project page for it. Explain in as much detail as possible how you made it, how it can be improved etc. Document it.

If you pick an advanced idea, setup a development roadmap and follow it. This will show some project management skills.

Another piece of advice for those who are design challenged. Use different front end frameworks and use different themes for those frameworks to provide appealing designs without looking like yet another bootstrap site.

jamesshenry

-- Two dashes start a one-line comment.

--[[
     Adding two ['s and ]'s makes it a
     multi-line comment.
--]]

----------------------------------------------------
-- 1. Variables and flow control.
----------------------------------------------------

jamesshenry

-- Two dashes start a one-line comment.

--[[
     Adding two ['s and ]'s makes it a
     multi-line comment.
--]]

----------------------------------------------------
-- 1. Variables and flow control.
----------------------------------------------------

jamesshenry

Conventional Commit Messages

See how a minor change to your commit message style can make a difference.

Tip

Have a look at git-conventional-commits , a CLI util to ensure these conventions and generate verion and changelogs

Commit Message Formats

Default

jamesshenry

$logFolder = "$PSScriptRoot\logs\"
# if (-not (Test-Path $logFolder)) { New-Item $logFolder -ItemType Directory }

$logPath = Join-Path -Path $logFolder -ChildPath "$((Get-Date).ToString("yyyy-MM-dd")).log"
if (-not (Test-Path $logPath)) { New-Item $logPath -ItemType File -Force }
Get-ChildItem $logFolder | ForEach-Object {
    if ($_.CreationTime -lt (Get-Date).AddDays(-7)) {
        Remove-Item $_.FullName
    }
}

jamesshenry

localdb: "Server=(localdb)\MSSQLLocalDB;Integrated Security=true;Initial Catalog=<SET_DB_NAME>"
postgresql: "Server=localhost;Port=5432;Database=my_db;Username=postgres;Password=postgres"

jamesshenry

if ((Test-Path .\.config\dotnet-tools.json) -eq $false) {
    dotnet new tool-manifest
}
dotnet tool install Husky
dotnet husky install
dotnet husky add commit-msg -c @"
dotnet husky run --name commit-message-linter --args "`$1"
"@
$huskyDir = "$PSScriptRoot\.husky"
$task = [PsCustomObject]@{