Skip to content

Instantly share code, notes, and snippets.

View taniomi's full-sized avatar
🤔

Milena Tanioka taniomi

🤔
View GitHub Profile
@taniomi
taniomi / get_unique_process_names.ps1
Last active October 7, 2025 17:11
Script to get unique process names for GlazeWM configuring
# List unique running processes names
Get-Process | Select-Object ProcessName | Sort-Object ProcessName -Unique
# If execution is blocked
Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass
@taniomi
taniomi / transform_template.py
Last active March 14, 2025 14:35
Transform: define data type template
bit_cols = [
'active',
'anonymousResponse',
'deleted',
'isAdditionalQuestion'
]
datetime2_cols = [
'date',
'answerDate'
]
@yinzara
yinzara / github_bitbucket_multiple_ssh_keys.md
Last active September 24, 2025 08:02
Managing SSH keys and repo cloning using multiple accounts on GitHub and BitBucket

Why Multiple SSH keys?

There are numerous reasons you may need to use multiple SSH keys for accessing GitHub and BitBucket

You may use the same computer for work and personal development and need to separate your work.

When acting as a consultant, it is common to have multiple GitHub and/or BitBucket accounts depending on which client you may be working for.

You may have different projects you're working on where you would like to segregate your access.

@qoomon
qoomon / conventional-commits-cheatsheet.md
Last active November 4, 2025 01:31
Conventional Commits Cheatsheet
@ilbunilcho
ilbunilcho / How to remove Windows paths from WSL path.md
Created November 1, 2018 16:41
How to remove Windows paths from WSL path

after Build 17093

  • can override settings by edit "/etc/wsl.conf"
  • normally this file is not exists at first
$ sudo vi /etc/wsl.conf

[interop]
appendWindowsPath = false
@nzakas
nzakas / gist:5511916
Created May 3, 2013 17:47
Using GitHub inside a company

I'm doing some research on how companies use GitHub Enterprise (or public GitHub) internally. If you can help out by answering a few questions, I'd greatly appreciate it.

  1. What is the primary setup? Is there an organization and each official repo is owned by that organization?
  2. Does every engineer have a fork of each repo they're working on?
  3. Are engineers allowed to push directly to the official repo? Or must all commits go through a pull request?
  4. Do engineers work on feature branches on the main repo or on their own forks?
  5. Do you require engineers to squash commits and rebase before merging?
  6. Overall, what is the workflow for getting a new commit into the main repository?
  7. What sort of hooks do you make use of?
  8. Are there any ops issues you encountered? (Scaling, unforeseen downtime, etc.)
@marchampson
marchampson / collaborator api
Created January 28, 2013 14:11
Add collaborator from command line
curl -i -u "my_user_name:my_password" -X PUT -d '' 'https://api.github.com/repos/my_gh_userid/my_repo/collaborators/my_collaborator_id'
@digitaljhelms
digitaljhelms / gist:4287848
Last active October 30, 2025 16:39
Git/GitHub branching standards & conventions

Branching

Quick Legend

Description, Instructions, Notes
Instance Branch