Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Setting up first project

Hi,

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.

 

Regards

Adrian

1 answer

1 accepted

0 votes
Answer accepted
Ana Retamal Atlassian Team Oct 22, 2018

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!

Kind regards,

Ana

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Sourcetree

Tip from the team: configure your repos for hosting goodness!

Supported Platforms macOS Windows We recently introduced support for additional hosting services such as GitHub Enterprise, GitLab (Cloud, Community Edition, Enterprise Edition), and...

3,390 views 4 5
Read article

Community Events

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

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you