Avatar of xathras1982
xathras1982
 asked on

How best to setup github repositories

Dear Experts,

I am looking for help and suggestions best practice for setup of your GitHub repo's.
Currently, my team has 1 central repository with multiple branches: master, release, hotfixes and features.

The team has expanded in size from a few people to 10 people and we've recently had a few events that have lead to merges being overwritten and lead to numerous discussions with the team on how they push code.

We have over 70 unique code objects to manage, each an executable that runs on the server from processes, reports, extracts and so on.
A recent idea I had was to break them up into logical feature groups such as:

Sales
Payment Reconciliation
Cash Reconciliation
Reporting[

If you were in my shoes how would you best approach?

Thank you in advance

Wayne
Version Control

Avatar of undefined
Last Comment
xathras1982

8/22/2022 - Mon
ASKER CERTIFIED SOLUTION
dinomix

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
GET A PERSONALIZED SOLUTION
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.
xathras1982

ASKER
Oh, I remember this. This is exactly where our starting point was :)
xathras1982

ASKER
Thank you for your feedback. Your response is perfect since your URL is exactly the best practice we started with.

It seems that we're in a good place with a start and need to find a best way to implement breaking up of the repos.
Experts Exchange has (a) saved my job multiple times, (b) saved me hours, days, and even weeks of work, and often (c) makes me look like a superhero! This place is MAGIC!
Walt Forbes