The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

repository

Per Jensen
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 27, 2019

i have a question regarding commit allowance.

ex. i have 2 seniors and 5 juniors.

i would like the seniors be able to the check what the juniors have commited before its commited to the repository.

and if ok the seniors can approve the commit .

 

did i make myself understandable?

 

1 answer

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

1 vote
Answer accepted
Christian Glockner
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 27, 2019

Hi Per,

 

In this kind of workflow you'd probably be best off using branches. Your juniors would be each be developing on their own branch, and once they think they're ready they push their changes to their branches and create a pull request and add the seniors as reviewers.

The seniors then review the pull request and if everything is fine they will approve and merge it to the master branch.

You could use branch permissions to prevent juniors fron pushing their code directly to the master branch and require them to open a pull request first.

 

Cheers,

Christian

Premier Support Engineer

Atlassian

Per Jensen
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 27, 2019

hi.

i'll set it up and see how they manage :)

thx

TAGS
AUG Leaders

Atlassian Community Events