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

"Changes Requested" should have a 'reset' event / button

I've come across this problem many times this week when a developer has raised a pull request in our codebase and someone has requested urgent changes. These changes are then made and pushed, but the "changes requested" flags still remain.


To combat this, should PR authors be given the ability to request a re-review once an update to the branch has been made, or should these flags just disappear when a new commit has been added since the flag was added – what do people think?

1 comment

I feel the need for a "re-review" request that could be made by the developer. 
Using the "Changes Requested" removes the PR from the "needs my review" list, and it should be added back there once the changes are made

Like # people like this


Log in or Sign up to comment

Atlassian Community Events