Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

×
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

Git Flow custom settings

I use Git Flow with my git repos. At the "start up" of the repo, after the clone I'll usually start pushing git flow button and configure it.

The new policies suggest to avoid the usage of "master" word for the production branch. So, like bitbucket suggest, I change all my production branches in "main".

There is a way to configure source tree to create the init form with custom values? I.E. now when you initalize the repository with the "Git Flow" button start with this values:

 

Production branch: master

Developer branch: develop

Feature branch: feature/

...

 

I'll prefer to start with different value, how can I customize these?

0 answers

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
TAGS
AUG Leaders

Atlassian Community Events