<div>
Oh, I remember this. This is exactly where our starting point was :)
</div>


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

<div>
Thank you for your feedback. Your response is perfect since your URL is exactly the best practice we started with. <br />
<br />
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.
</div>


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.

<div>
<div class="content wysiwyg-content">
Dear Experts,<br />
<br />
I am looking for help and suggestions best practice for setup of your GitHub repo's. <br />
Currently, my team has 1 central repository with multiple branches: master, release, hotfixes and features.<br />
<br />
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.<br />
<br />
We have over 70 unique code objects to manage, each an executable that runs on the server from processes, reports, extracts and so on. <br />
A recent idea I had was to break them up into logical feature groups such as:<br />
<br />

<div class="bullet">
Sales
</div>
<div class="bullet">
Payment Reconciliation
</div>
<div class="bullet">
Cash Reconciliation
</div>
<div class="bullet">
Reporting[
</div>
<br />
If you were in my shoes how would you best approach? <br />
<br />
Thank you in advance<br />
<br />
Wayne
</div>
</div>


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

How best to setup github repositories

Version control, also known as revision control or source control, is the management of changes to documents, computer programs, large web sites, and other collections of information. Changes are usually identified by a number or letter code, termed the "revision number," "revision level," or simply "revision." Version control systems (VCS) most commonly run as stand-alone applications, but revision control is also embedded in various types of software such as word processors and spreadsheets, and in various content management systems. Revision control allows for the ability to revert a document to a previous revision. Git, a widely-used VCS, has its own topic; other popular systems include CVS, Subversion, Team Foundation Server (TFS), Visual SourceSafe (VSS) and Perforce.