Using two environments pointing at same repo?

[Grumpster-Dev]

I am a rank noob on github - currently working through the git course on boot.dev. I have a macOS machine and a Linux (Ubuntu) machine, and am tinkering with doing commits on the same project from either. Will this cause clashes? The path from root to the project path is different on each, but the folder for all my git related code is at ~/github_projects on both machines. If I start working on one machine, do a few commits, and then switch to the other machine, develop new code, then commit, will this break the git archive?

Are there a set of best practices for this? It is not truly open source, as I am the only person involved, but I am guessing that there is a way to accomplish this, without 'stepping on my own feet' so to speak?

Any and all responses are warmly welcomed!

ADVthanksANCE

[shimauma0312]

hi @Grumpster-Dev

Git is designed for distributed work, so using both your macOS and Ubuntu boxes on one project won’t break anything—if you keep them in sync.

1. Single Source of Truth
   Host one remote repo (e.g., on GitHub) and clone it on each machine.

2. Identify Yourself Once

   git config --global user.name  "Your Name"
   git config --global user.email you@example.com

3. Before You Code

   git pull   # grab any commits pushed from the other computer

4. After You Code

   git add .
   git commit -m "Describe the change"
   git push   # make the work available to the other machine

5. Ignore OS Junk
   Add items like .DS_Store or *~ to .gitignore.

6. Mind Case Sensitivity
   macOS (default) is case-insensitive; Linux is not. Avoid files that differ only by letter case.

7. Consistent Line Endings
   On both machines, set

   git config --global core.autocrlf input   # or just leave it off

TL;DR

clone → pull → code → commit → push → repeat

Conflicts only appear if you edit the same lines on both machines without pulling first. Follow the rhythm above and your repository—and sanity—remain intact.

[Grumpster-Dev]

Thank you for your timely, and helpful response. I will strive to adopt these procedures going forward!

[mayur-driod]

Hey @Grumpster-Dev,
Yes, what you described is totally doable, and Git is specifically designed to handle this kind of workflow. Here's a breakdown with some advice:

General Workflow Advice

As long as you consistently pull and push changes, you won’t break anything. Git is made for version control across multiple devices, users, and branches, even if the folder paths differ between systems.

Golden Rule:
Before starting work on a new machine, always git pull to ensure you have the latest changes. After you're done, git add, commit, and push your updates back.

This ensures both machines stay in sync and you don’t run into merge conflicts, or at least you keep them easy to manage.

---

On Dependencies (like React or Node.js projects)

If you're using tools like React and installing dependencies (e.g., react-icons, express, etc.), those packages usually go into a node_modules folder, which is not tracked by Git (and shouldn’t be). Instead, those dependencies are listed in package.json.

So when switching machines:

• Run npm install or yarn install to make sure all required packages are installed locally based on package.json.
• That keeps your project runnable even after pulling it to a new machine.

---

Best Practices for Solo Cross-Device Development

Here are a few tips to keep things smooth:

1. .gitignore properly – Make sure OS-specific or IDE-specific files (like .DS_Store, .vscode, etc.) are ignored in both environments.
2. Use SSH keys or Personal Access Tokens (PATs) for authentication with GitHub to make pushes/pulls seamless on both machines.
3. Consistent commits – Use clear commit messages so you can trace what happened and when.
4. Optional: Use branches if you want to experiment on one machine without affecting the main branch until you're ready.

---

GitHub isn’t going to break if you push from two places. Even if you do run into a merge conflict (say you edited the same file differently on both machines), Git will clearly tell you and let you resolve it.

You're not “stepping on your own feet” you're learning to juggle tools like a pro :). Just keep that push/pull flow in mind, and you’ll be fine.

Basically:
clone → pull → install (if dependencies change) → code → commit → push → repeat
as described by @shimauma0312

[Grumpster-Dev]

Thank you mayur-driod! This helps greatly. Nice extension of what @shimauma0312 suggested. I will use this thread going forward with my git journey. I am still in the early stages of the course on boot.dev and just coming up on the clone and pull commands.... Nice to get a real world preview of how and why to implement them. Appreciate your feedback.

[mayur-driod]

Hey @Grumpster-Dev ,
If you think this thread answered your question then please mark it as answered :)

[Grumpster-Dev]

Done