By 'we cannot get past the basics to git page', do you mean the 'You have an empty repository page'? If so, it sounds like hooks aren't being triggered when you push to the repository (a cache controlling the 'empty' check should be invalidated when a push happens). Can you open a support request on https://support.atlassian.com and upload a support zip (Admin > Atlassian Support Tools > Support Zip) so we can have a look at your logs etc?
As Michael mentioned, you need to push your commits to Stash after committing to your local repo with your Sourcetree. Please refer to Importing code from an existing project.
Just giving more insight on the hook issue mentioned by Michael, you could try to look into the quirks we found and published on: Pull Requests Not Reflecting Changes Pushed to Remote Branch After an Upgrade. The effect on the KB is different to what you describe but the cause (hooks permission) is the same.
Feel free to raise an issue in SAC and we will look into it for you.
I hope these details help.
Just as a precautionary measure since I don't know where you stand on the 'new to git' to 'git guru' scale - after committing, you run 'git push' to move your code from your local computer up to Stash, right? And the output of the push command shows no errors? SourceTree works on your local computer so will show the commits even before they are pushed.
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot