I am very new to this and am just about to set up my first Repository and have a few questions on best practice.
I am going to create a MASTER repository that contain all my source code (Oracle based), PL/SQL packages, table scripts, FNDLOAD items etc.
From this I want to create Projects, which are effectively bug fixes or enhancements to code. These projects will include code changes, UAT Testing, SIT Testing, AT Testing and finally released back to MASTER.
I'm thinking that for each 'Project' I simply create a separate repository off the MASTER repository which includes the code etc that needs changing.
From each of these Project Repositories I will create a separate Sub-Branch(?) for each of the testing cycles (which may require the code to be changed again).
Once all the testing cycles have been completed (and approved) the code can be pushed back to MASTER to be released.
Does this sound like the best way to do things or do you have any other suggestions.
Hi Adrian, welcome to the Community!
This doesn't sound like a Sourcetree question, but instead more of like a 'Git best-practice' question, assuming you're using Git.
I believe what you want is to have a repository where all your code will be and then have separate branches for each feature or "project". Once you've tested your feature, you can merge it to the main branch. Git doesn't use the term "project" so you'll need to adapt it to how it better suits you.
Another thing you might want to look at are Git submodules, you can read more here.
Hope that helps!
A vulnerability has been published today in regards to Sourcetree for Windows. The goal of this article is to give you a summary of information we have gathered from Atlassian Community as a st...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event