I have a master development branch, from which 2 resources have taken up 2 tasks. Resource A has completed his task and has merged his task to the main trunk. Resource B still is continuing his work. He sees that there is a pull request available to pull the work of Resource A.
Somehow this pull request doesn't seem to pull the required changes. Please advise the following:
- Are these specific settings/configuration/checklist items that I need to be aware of in such scenarios?
- Are there defined best practices that we can review to ensure that we don't hit upon any issues?
Apologies if I've misunderstood, but Resource B will only be able to see the changes made by Resource A if either
If they have not been merged then to see the other Resource's branch and their changes they would each need to check out the other one's branch
There is some additional information here
A vulnerability has been published today in regards to Sourcetree for Windows. The goal of this article is to give you a summary of information we have gathered from Atlassian Community as a st...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event