Home/ Questions/Q 4544556
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-21T15:41:17+00:00

I’m new to the Git world but I realize that, since my programmer and

  • 0

I’m new to the Git world but I realize that, since my programmer and I are going to be working on files at the same time, we need to establish a Git workflow. I have very minimal experience with Git from a 3 month project I did last year so I need help setting this up.

Currently, I have an account at a web host where all the current project files exist. I typically modify the files remotely using Coda connected to the server.

We purchased a month of service at Github to create a private repository so that we can use the GUI feedback of Github to solve bugs using the pretty UI to see the diffs.

On the web host account, no Git repository is setup yet. I do not completely understand how to transfer the files to Github but I assume I would need to create a repository on the web host account first and then push this to the Github account.

Does this sound correct? Which account would we set as the master repository? Beyond what I wrote, I am not sure I completely understand how to do every or if there’s a better way to do what I’ve explained.

I’d appreciate your feedback and if possible someone to write explicit instructions on how to do this. Thanks!

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    When working with GitHub repo, you have two choices:

    • add your team as collaborator for your repo (they can push directly to said repo)
    • ask them to fork your repo (clone on the GitHub side), then making pull requests in order for you to integrate their changes.

    Since we are talking private repo, the first solution is more practical (to avoid having to setup different private, i.e. not free, repos for each developers).

    From there you need to setup a branch/merge workflow decide if you want, for a given development effort where several people work on the same set of files, if:

    • each developers will work on the same common branch (in which case they need to rebase and resolve any conflict locally, before pushing their commits)
    • each developers will work on a user-specific branch (in which case, they can push whenever they want, but an integrator will have to pull said branches and do the merge).

    (see also “when should you branch?” and the second part of “Why uses git fast-forward merging per default?“)

    • 0