Skip to content

Instantly share code, notes, and snippets.

View kalihman's full-sized avatar
🐵

YJ Song kalihman

🐵
View GitHub Profile
### Keybase proof
I hereby claim:
* I am kalihman on github.
* I am kalihman (https://keybase.io/kalihman) on keybase.
* I have a public key ASDt-9JBWfIFqebzAMl5uJkdbIwsJ64c9SdHp0fKkQ-L6Qo
To claim this, I am signing this object:
@kalihman
kalihman / AWS4-Request-Signer.ps1
Last active November 2, 2023 05:15
Powershell AWS4 Signer for STS GetCallerIdentity Action
# Define Helper Functions
function Get-Sha256Hash ($StringToHash) {
$hasher = [System.Security.Cryptography.SHA256]::Create()
$Hash = ([BitConverter]::ToString($hasher.ComputeHash([Text.Encoding]::UTF8.GetBytes($StringToHash))) -replace '-','').ToLower()
Write-Output $Hash
}
function ConvertTo-SortedDictionary($HashTable) {
$SortedDictionary = New-Object 'System.Collections.Generic.SortedDictionary[string, string]'
foreach ($Key in $HashTable.Keys) {
@kalihman
kalihman / GitHub-Forking.md
Created July 28, 2020 11:11 — forked from Chaser324/GitHub-Forking.md
GitHub Standard Fork & Pull Request Workflow

Whether you're trying to give back to the open source community or collaborating on your own projects, knowing how to properly fork and generate pull requests is essential. Unfortunately, it's quite easy to make mistakes or not know what you should do when you're initially learning the process. I know that I certainly had considerable initial trouble with it, and I found a lot of the information on GitHub and around the internet to be rather piecemeal and incomplete - part of the process described here, another there, common hangups in a different place, and so on.

In an attempt to coallate this information for myself and others, this short tutorial is what I've found to be fairly standard procedure for creating a fork, doing your work, issuing a pull request, and merging that pull request back into the original project.

Creating a Fork

Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or j