feat: Update Tips And Tricks

Signed-off-by: https://github.com/Someshdiwan <[email protected]>

Author: Someshdiwan

Tips And Tricks/git.txt renamed to Tips And Tricks/Git.txt

@@ -1,7 +1,3 @@
-Nice — here’s the commit graph diagram you asked for. This shows how your history looks depending on whether you merge or rebase.
-
-⸻
-
 A) Merge workflow (preserves full branch graph)
 
 Upstream main:   A──B──C───────────────┐
@@ -82,5 +78,3 @@ So: Merge = “historical diary” (records exactly what happened).
 Rebase = “rewrite the story” (makes it look like you developed cleanly on top).
 
 ⸻
-
-Want me to also sketch a real-life example with commit hashes (like abc123, def456) so you can see how git log looks different between merge and rebase?

Tips And Tricks/Github.txt

@@ -1,7 +1,3 @@
-Perfect — here’s a visual ASCII diagram showing how forks, remotes, branches, and PRs fit together. This is the “map in your head” for push/pull/rebase.
-
-⸻
-
 GitHub Fork Workflow — Visual Map
 
                  ┌─────────────────────────────────────────┐
@@ -79,9 +75,3 @@ git push origin feature-branch --force-with-lease
 
 
 ⸻
-
-👉 This diagram shows the two “worlds”: your fork (origin) and the official repo (upstream). Your feature-branch is only in your fork until you open a PR. After merge, the changes live in upstream’s main.
-
-⸻
-
-Would you like me to also show a commit graph diagram (with merge vs rebase paths) so you can see how history looks in both cases?

Tips And Tricks/GithubWorking.txt

@@ -1,13 +1,3 @@
-Yes, we can definitely turn this into a clean anonymous one-page GitHub/Git workflow cheat sheet — no JetBrains, no school references, just the structure + universal commands.
-
-Here’s a refined version:
-
-⸻
-
-GitHub/Git Pro Workflow Cheat Sheet
-
-⸻
-
 1) GitHub Hierarchy
 
 GitHub (service)
@@ -125,7 +115,3 @@ Fork repo → Clone → Create branch → Commit → Push → Open PR
 
 
 ⸻
-
-This way, you’ve got the hierarchy, commands, and etiquette in one page.
-
-Would you like me to make a visual ASCII diagram of remotes/branches (origin vs upstream, main vs feature branch) so you can instantly see where push/pull/rebase happen?