I’ve noticed that my learning path isn’t always linear (to say the least) — I tend to jump between topics depending on life and mood. I still document everything I study, but without context it can feel a bit scattered for a reader.

To make things clearer, I’ll start adding a short line at the beginning of each post to briefly highlight what I actually focused on that day, before going into the usual sections like goals, lessons learned, and so on.

👉 Topic: GitHub / repo / CLI confusion (real workflow issue)

🎯 Goal

Clarify how GitHub authentication works and understand the relationship between remote repositories and local copies.

🔄 Context Switch

After several days exploring AI systems, today I switched back to practical development workflow issues, specifically GitHub and local repository management.

🛠 What I Did

I encountered confusion while trying to work with a repository that existed on GitHub but not locally.

I:

  • authenticated using gh auth login
  • checked remote configuration with:

git remote -v

  • questioned whether I needed to re-clone repositories after authentication

🔗 Key Cybersecurity Connections

Understanding Git workflows is important for:

  • maintaining code integrity
  • tracking changes during incident investigations
  • avoiding accidental exposure or mismanagement of repositories

In real environments, poor Git hygiene can lead to:

  • credential leaks
  • unauthorized access
  • supply chain risks

🔍 Investigation Questions

  • Where is the actual source of truth (local vs remote)?
  • Is the repository correctly cloned and linked?
  • Are credentials being handled securely?

🚨 Detection Opportunities

  • detect suspicious pushes to repositories
  • monitor unusual authentication events
  • identify access from unknown devices

🧭 MITRE ATT&CK Techniques

  • T1552 — Unsecured Credentials
  • T1195 — Supply Chain Compromise

⚠ Challenges

The main confusion was conceptual:

  • authentication ≠ repository presence
  • logging in does not download code

📚 What I Learned

  • GitHub authentication only grants access
  • cloning is required to create a local working copy
  • remote origin defines where code is pushed/pulled

➡ Next Steps

  • deepen understanding of branching and workflows
  • explore secure repository practices

🧠 Reflection

This highlighted how easy it is to misunderstand tools when focusing only on commands instead of underlying concepts.

🧩 Lessons Learned

What worked

Verifying configuration using CLI commands.

What broke

Assuming authentication automatically syncs repositories.

Why it broke

Misunderstanding of Git architecture.

Fix / takeaway

Always distinguish between access, storage, and synchronization.

📈 Skill Progression Context

This improves operational discipline and reinforces secure development practices.