Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

When you initialise GitFlow is there a way to commit the changes?

Hands up - I'm a double noob - new to Git and SourceTree.

We are migrating from SVN to Git and we've chosen SourceTree as the primary UI tool and plan to use GitFlow for a branching process.

After a lot of attempts I've got the test migration sorted so switched my attention more to SourceTree. When you click the "Git Flow" button in the toolbar the options to fill out (or accept defaults) is straightforward and fits perfectly with the articles I've read about the Git Flow process. When confirming the configuration it fails to initiate if there are any unstaged and/or uncommitted files.

My question is: once initiated successfully is there a way to put the change to the git config file back in the central repo? I don't want every person on the team to have to set this up. But SourceTree says there are no outstanding files to commit


0 answers

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events