[go: up one dir, main page]

Release Update 01/22/2025

Salesforce

PR Validation Dashboard - A centralized Interface to Manage and Track PR Validations and Activity

Opsera's Pull Request (PR) Validation Dashboard simplifies and streamlines PR management within development teams. It offers a centralized platform where teams can manage and track Pull Request activities seamlessly, across projects.

The dashboard provides real-time visibility into the status of all PRs, enabling users to quickly identify successful and failed validations. Each PR comes with detailed summary, console logs and reports. Users can also run pre-validations directly from this dashboard, before finalizing their PRs. With detailed Activity Logs available for each PR, users can keep track of the recent PR changes and maintain an audit trail. The activity logs can also be customized according to your specific need by setting up custom filters.

Contact Opsera support to activate the PR Validation Dashboard for your organization and start experiencing the benefits of streamlined PR management.

Capability to Perform Pre Validation on Pull Request (PR)

The PR Validation feature is introduced to streamline the process of assessing code changes before they are merged into the main codebase. This capability allows developers to run pre-validation checks on Pull Requests directly from their dedicated PR Validation dashboard.

Users have the ability to select specific branches from their Source Control Management (SCM) accounts for validation. The criteria for these Pull Request Validations are governed by Repository Rules that you must establish to define your Organization’s validation standards.

Upon successful/failed validations on a pull request, developers receive comprehensive status reports and summary detailing the results of each check performed during the validation process. You can utilize this feature to provide actionable insights into what aspects of the code may need attention and help your developers to identify areas that require fixes or further testing based on these reports.

Capability to Format JSON and XML Files While Solving Merge Sync Conflicts

A capability is introduced for users to format JSON and XML files shown on the merge conflict resolution screen, within their Git to Git task workflow. Formatting JSON typically involves indentation and line breaks that make the structure of data clear, and XML can be visually nested. With this capability, users get a well-formatted view that helps highlight discrepancies between different versions of the files, making it easier for users to pinpoint where changes have occurred.

Please note that this formatting feature does not revert formatted files back to their original unformatted state.

Last updated

Was this helpful?