Merge Requests
We fixed the bug. We completed the feature. We underestimated the effort of our task and want to integrate the first code changes. Regardless, it works on our machine and we're ready to integrate our changes into the main branch. To ensure we only merge high-quality code into our main branch and ultimately our product, we scrutinize any additions into our trunk via a gate-keeping mechanism called a Merge Request (MR). All serious source control platforms offer automation, tooling, and UIs for creating and reviewing MRs.
A MR allows developers to provide context for their changes. We can provide information as to why the new code was necessary, attach links to tickets and bug reports, and provide any media to explain the expected behavior. We run automated tools and automated tests and request manual and AI driven code reviews. MRs are the first milestone in the life cycle of a code change for continuous integration.
-
Good read? Unlock the rest.
Engineering Collaboration is still in development and currently only available as an Advanced Reading Copy for select readers.