Home/ Questions/Q 658867
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-13T22:58:50+00:00

I have a central git repository that everyone pushes to for testing and integration,

  • 0

I have a central git repository that everyone pushes to for testing and integration, but it only is pushed to when features are ‘ready’. While in the middle of a big task, developers frequently have many commits that stay on their hard drives.

Sometimes in the middle of these projects I’d like to either see what another developer is doing, or show him how I’ve done something. I’d like to be able to tell another developer to just “pull my working copy”.

The only way I can think of is having everyone run SSH on their development machines and adding accounts or SSH keys for everyone, but this is a huge privacy and permissions nightmare, and seems like a lot of work to maintain.

Should we just be pushing to that central repository in these cases? Should we be pushing after every local commit?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Two common approaches:

    • developers have their own public repos (for example mpd and associated programs).
    • developers push to refs in their own namespace on a central repo (dev1/master, dev2/master). Depending on your exact situation, you might want some access control in the form of hooks to make sure no one does anything silly.
    • 0