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

Workflow-Cloning & Pushing instead of Pull Requests

Please pardon me for posting a very basic question. I did look around quite a bit if this question has been answered and I could see anything except so I had to ask this.

We are planning to have a small team of temporary contractors (that will perhaps change every couple of months or so) for our repository and since it is difficult for us to keep on requiring everyone to learn to create pull requests, we are going to default to the option of requiring people to push their changes directly from the local repository to the cloud repository.


I just wanted to make sure that it is possible that without any repercussions later on in the workflow at this stage. I know that Atlassian really wants to use pull requests and I just wanted to make sure that we do not run into any problems using that.

(I do not have any means to run a simulation also right now, so had to ask this) thank you for any inputs



Log in or Sign up to comment
AUG Leaders

Atlassian Community Events