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

How do I permanently remove very long commit message while trying to resolve conflicts?

When I do a very large merge the commit message lists every file being merged.  This message becomes so large that you can't see the stage/unstage file frames and can NOT scroll the window.  The only work-around is to highlight the entire commit message and remove it... this makes the stage/unstage frames accessible.  BUT, once you perform some other operation (say, try to resolve conflicts on some files), the very large commit message returns.  And this causes the stage/unstage frames to disappear.  This happens EVERY time and is very frustrating and unproductive.  I need help on this ASAP!!! Otherwise, this will literally take me hours to do a merge.

1 answer

0 votes
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jan 25, 2019


We have a fix in the pipeline for the very large textbox obscuring the file listing. It should be coming in 3.1.

I've created to cover this, because I thin we still need to investigate the re-occurance of the message after you've edited it.

I'm looking forward to the fix in v3.1.  Thank you for opening another JIRA defect for the reoccurring message after its been edited.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events