start new:
tmux
start new with session name:
tmux new -s myname
| $ git config --global --add alias.lol "log --graph --decorate --pretty=oneline --abbrev-commit --all" | |
| $ git lol | |
| * 9f0349d (HEAD, origin/master, origin/HEAD, master) Now finally does frickin pull first. | |
| * 1cc98b0 Added auto-update. | |
| * 405970a Initial import. |
| # --------------------------------------------------------------------------- | |
| # | |
| # Description: This file holds all my BASH configurations and aliases | |
| # | |
| # Sections: | |
| # 1. Environment Configuration | |
| # 2. Make Terminal Better (remapping defaults and adding functionality) | |
| # 3. File and Folder Management | |
| # 4. Searching | |
| # 5. Process Management |
| [credential] | |
| helper = cache --timeout=99999999999999999 | |
| [user] | |
| name = Firstname Lastname | |
| email = [email protected] | |
| [alias] | |
| lol = log --graph --decorate --pretty=oneline --abbrev-commit --all | |
| glog = log --graph --pretty=format:'%Cred%h%Creset -%C(yellow)%d%Creset %s %Cgreen(%cr) %C(bold blue)<%an>%Creset' | |
| log-file = log --follow --color -- | |
| co = checkout |
Please comment below if you are using Kubernetes Third-Party Resources and I will add you to the list.
Known Users:
There are three easy to make mistakes in go. I present them here in the way they are often found in the wild, not in the way that is easiest to understand.
All three of these mistakes have been made in Kubernetes code, getting past code review at least once each that I know of.
What do these lines do? Make predictions and then scroll down.
func print(pi *int) { fmt.Println(*pi) }| You are a powerful agentic AI coding assistant, powered by Claude 3.5 Sonnet. You operate exclusively in Cursor, the world's best IDE. | |
| You are pair programming with a USER to solve their coding task. | |
| The task may require creating a new codebase, modifying or debugging an existing codebase, or simply answering a question. | |
| Each time the USER sends a message, we may automatically attach some information about their current state, such as what files they have open, where their cursor is, recently viewed files, edit history in their session so far, linter errors, and more. | |
| This information may or may not be relevant to the coding task, it is up for you to decide. | |
| Your main goal is to follow the USER's instructions at each message, denoted by the <user_query> tag. | |
| <communication> | |
| 1. Be conversational but professional. |