🪄 Improved 🖼️ UX/UI 🎨 Design area
over 1 year ago

⧮ Improve PR/MR* creation flow with clear error messages!

*
PR = Pull Requests
MR = Merge Requests

Brainboard's tech team has significantly improved the error messaging experience when performing pull or merge requests.

To accomplish this, we have changed the backend to provide more detailed and informative error messages. These error messages are now displayed directly on the front end, making it easy for you to understand and resolve any issues that may arise. We have also made improvements to the modal's User Experience (UX) to make it more intuitive and user-friendly. 

These enhancements will make it easier for you to manage and troubleshoot your code changes.


About

Merge requests (MRs) & pull requests (PR) in a version control system (VCS) like Git can save your cloud infrastructure project by allowing you to:

  1. Collaborate effectively with team members: PR/MR provide a way for team members to propose changes to the infrastructure codebase and review and discuss them with other team members before merging them into the main branch. This allows for better collaboration and communication within the team.
  2. Implement code review and testing processes: PR/MR provides a way to implement a code review process, where other team members review changes to the infrastructure codebase before being merged. This can help identify and fix bugs and issues before they are deployed to production.
  3. Track changes to the infrastructure codebase: PR/MR provides a way to track changes to the codebase, including who made the change and why making it easier to understand how the infrastructure has evolved.
  4. Rollback changes: PR/MR provides a way to roll back changes to the infrastructure codebase if something goes wrong. This can be done by reverting the merge commit or using version control tools like Git to revert specific changes.
  5. Isolate changes: PR/MR provides a way to isolate changes, meaning that changes are committed and tested in a separate branch before merging into the main branch. This allows for keeping the main branch stable and ready to deploy at all times.
  6. Implement automated testing and integration: PR/MR provides a way to implement an automated testing and integration process. This can be done by integrating the VCS with a continuous integration and deployment tool, which can run automated tests and deploy changes to different environments.

One step forward binary way of working the infrastructure on Brainboard.