cool tag line goes here...

Understanding SQL joins, Eloquent relationships, and model accessors. 1) Join (Database level) A join is a database operation used to combine rows from multiple tables. It happens at the SQL level and is focused on performance and filtering. Example: SELECT users.name, posts.title FROM users JOIN posts ON posts.user_id = users.id; Runs in the database Returns raw rows Very fast 2) Relationship (Eloquent ORM level) A relationship defines how models are connected. It represents business meaning, not just raw data. class User extends Model { public function posts() { return $this->hasMany(Post::class); } } Usage: $user->posts; Returns model objects Supports lazy & eager loading Encodes domain logic 3) Model Accessor (Presentation level) An accessor is a computed attribute on a model. It does not fetch data from the dat...

You can compare only the files that differ between your current local branch and another branch on the remote using Git. Here are the most common and useful ways, from simplest to more detailed. 1. List only the changed files (most common) git fetch origin git diff --name-only origin/other-branch If you want to be explicit about your current branch: git diff --name-only origin/other-branch..HEAD ➡️ Shows only file paths that are different. 2. List changed files with change type (added / modified / deleted) git diff --name-status origin/other-branch..HEAD Example output: M src/app.js A src/new-file.ts D src/old-file.css 3. Compare against the common ancestor (recommended for PR-style comparison) This avoids noise from changes made in the target branch after you branched. git diff --name-only origin/other-branch...HEAD ... (three dots) means: changes on your branch since it diverged from the other branch This is usually what you want when prepari...

Here’s a clean step-by-step way to compare your local WSL repo folder vs the remote repo state in WinMerge , and then show only changed files . 1) In WSL: go to your repo and fetch remote cd /path/to/your/repo git fetch origin 2) In WSL: create a “remote snapshot” folder (safe, no checkout) This exports the remote branch into a temp folder. REMOTE_BRANCH=origin/main SNAP=/tmp/repo_remote_snapshot rm -rf " $SNAP " mkdir -p " $SNAP " git archive " $REMOTE_BRANCH " | tar -x -C " $SNAP " Change origin/main if your remote branch is different (e.g. origin/master , origin/develop ). 3) Open WinMerge and start a folder compare Launch WinMerge (on Windows) File → Open… (or “Open”) Select Folder Compare 4) Pick the two folders (WSL paths via \\wsl$ ) In WinMerge: Left (Local working folder) Use your actual repo path in WSL: \\wsl$\Ubuntu\home\<youruser>\ path \ to \your\repo Right (Remote snapshot folder) \\wsl $ \Ubu...

  If you want to revert everything back to the last commit and discard all local changes , use this 👇 🔥 Hard reset (most common & safest) This restores your working tree and index to the latest commit . git reset --hard HEAD What this does ❌ Discards all modified files ❌ Discards all staged files ❌ Discards all untracked changes in tracked files ✅ Leaves your repo exactly as the last commit 🧹 Also remove untracked files (optional but often needed) If you also want to delete untracked files and folders : git clean -fd Or preview first (recommended): git clean -fdn ✅ One-liner (full nuclear option) git reset --hard HEAD && git clean -fd ⚠️ Important warning This is irreversible unless: Changes were committed Or stashed Or still exist elsewhere

✅ SAFE (Recommended): Revert the pushed commit Find the commit you pushed git log --oneline Copy the commit hash (e.g. abc1234 ). Revert that commit git revert abc1234 Git creates a new commit that undoes the changes. If multiple commits: git revert abc1234..HEAD Push the revert git push ✅ Best practice for shared branches ⚠️ DANGEROUS (Only if you are 100% sure) Use this only if you are the only one working on the branch or it’s a personal feature branch: Reset and force-push git reset --hard HEAD~1 git push --force This will remove the commit locally and rewrite remote history ❌. If the pushed commit was a deletion and you want to restore a file: git checkout HEAD~1 -- path/to/file git commit -m "Restore accidentally deleted file" git push Which one should YOU use? Situation Command Shared branch git revert <commit> ...

You can revert just that single file from other remote branch without touching anything else. Option 1: Restore file from remote branch (recommended) git fetch origin git checkout origin/[remote_branch] -- file_path_in_GIT This will: Take the version of the file from remote origin/[remote_branch] Overwrite your local copy Leave you on your current branch Then commit it: git commit -m "Revert file from other branch" Option 2: If your local branch is already tracking the remote branch You can shorten it to: git checkout [remote_branch] -- file_path_in_GIT (Still followed by a commit.) Option 3: Using modern git restore (Git ≥ 2.23) git fetch origin git restore --source=origin/[remote_branch] -- file_path_in_GIT Then commit: git commit -m " Revert file from other branch" Verify before committing (optional but smart) git diff ⚠️ Notes This does not switch branches This does not affec...

alias ll="ls -lah" alias branch="git branch" alias checkout="git checkout" commit() { echo "Enter commit message (Ctrl+D to finish):" msg=$(cat) git commit -m "$msg" } add() { # Ensure git repo git rev-parse --is-inside-work-tree >/dev/null 2>&1 || return 0 # Colors GREEN="\e[32m" RED="\e[31m" YELLOW="\e[33m" CYAN="\e[36m" BOLD="\e[1m" RESET="\e[0m" local current_branch remote_branch behind local files file answer local added_files=() local skipped_files=() local temp_ignored_files=() local existing_temp_ignored=() current_branch=$(git branch --show-current) # ---------- STEP 0: Check existing temp-ignore files ---------- mapfile -t existing_temp_ignored /dev/null 2>&1 || { echo -e "${RED}Fetch failed.${RESET}" return 1 } behind=$(git rev-list --count HEAD.."$remote_branch" ...