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

Some case insensitive patterns in .gitattributes ignored by sourcetree?


For projects I use a .gitattributes file which contains lines for defining file extensions which should be tracked by LFS. It looks like:

*.[pP][nN][gG] filter=lfs diff=lfs merge=lfs -text
*.[tT][iI][fF] filter=lfs diff=lfs merge=lfs -text
*.[fF][bB][xX] filter=lfs diff=lfs merge=lfs -text

*.[tT][aA][rR].[gG][zZ] filter=lfs diff=lfs merge=lfs -text
*.[zZ][iI][pP] filter=lfs diff=lfs merge=lfs -tex

I do this, as some applications spit out files with uppercase extensions, and some lowercase.

But the last 2 patterns are not working in sourcetree (maybe more won't work, but haven't checked everything); sourcetree shows a dialog window which states .zip files not being tracked by LFS, with the option to Cancel or to Add anyway. Everything works as expected using the command line tools, haven't checked if I just Add anyway if things goes well...

Is there some setting in sourcetree which prevents using some of these patterns? Or is this is a bug in sourcetree?


0 answers

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events