Keeping track of pull requests
A common feature of DevOps practices is the use of the so-called trunk-based development method, which is a key enabler for the application of Continuous Integration and Continuous Delivery or Development (CI/CD) to the software development process.
One of the ways to achieve this is by making use of short-lived branches taken from the master (or trunk) branch to perform development tasks. Jira facilitates this by allowing developers to automatically create branches for each development task when a source control repository such as Bitbucket or GitHub is configured for the software project.
These short-lived branches are usually merged back into the master/trunk branch by way of pull requests, which allow developers to review the changes introduced into the software before merging them into the master branch.
In this section, we will see how using automation rules allows us to keep track of these pull requests, which typically happen directly...
