Repository navigation
Qa - #88
Merged
Merged
Qa#88
Conversation
…#67) * Update dependencies and enhance CI workflow - Upgraded `express` to version `4.22.3` and `qs` to version `6.16.0` to address security vulnerabilities. - Updated CI workflow to include separate steps for auditing dependencies at different severity levels and improved Docker image builds with Trivy scanning. - Documented changes in the CI process and dependency management in the project wiki. * Enhance CI workflow with improved Docker image scanning - Added comments to clarify the build process and updated Trivy configuration to skip specific directories, addressing issues with high-severity vulnerabilities in node_modules. This change aims to streamline the CI process while maintaining security standards.
…anagement - Introduced `OperationManager` to handle in-process Git operations, managing operation states and durations. - Implemented `RepositoryOperationLock` to serialize incompatible mutations by repository, allowing concurrent operations on different repositories. - Updated `GitUseCases` to utilize the new operation manager for executing Git commands, enhancing error handling and progress tracking. - Added tests for `OperationManager` and `RepositoryOperationLock` to ensure correct operation under various scenarios, including successful merges, conflicts, and concurrent executions. - Refactored existing code to integrate the new management system, improving overall structure and maintainability. - Updated documentation to reflect changes in the Git operations architecture and usage.
…anagement - Introduced `OperationManager` to handle in-process Git operations, managing operation states and durations. - Implemented `RepositoryOperationLock` to serialize incompatible mutations by repository, allowing concurrent operations on different repositories. - Updated `GitUseCases` to utilize the new operation manager for executing Git commands, enhancing error handling and progress tracking. - Added tests for `OperationManager` and `RepositoryOperationLock` to ensure correct operation under various scenarios, including successful merges, conflicts, and concurrent executions. - Refactored existing code to integrate the new management system, improving overall structure and maintainability. - Updated documentation to reflect changes in the Git operations architecture and usage.
…nts - Added `programarPush`, `programarPull`, and `programarFetch` methods to `GitUseCases` for non-blocking Git operations. - Introduced `vistaOperacion` for standardized operation views, ensuring metadata is excluded from responses. - Updated `GitController` to utilize new methods, returning operation status immediately with a 202 response. - Enhanced tests for `OperationManager` and `GitController` to cover new asynchronous behaviors and ensure correct operation tracking. - Updated documentation to reflect changes in Git operations and HTTP API structure.
Se conserva el OperationManager asincrono del bloque D. qa traia una copia paralela del motor del bloque C en los mismos archivos. Co-authored-by: Cursor <cursoragent@cursor.com>
…nts - Added `programarPush`, `programarPull`, and `programarFetch` methods to `GitUseCases` for non-blocking Git operations. - Introduced `vistaOperacion` for standardized operation views, ensuring metadata is excluded from responses. - Updated `GitController` to utilize new methods, returning operation status immediately with a 202 response. - Enhanced tests for `OperationManager` and `GitController` to cover new asynchronous behaviors and ensure correct operation tracking. - Updated documentation to reflect changes in Git operations and HTTP API structure.
Se conserva el OperationManager asincrono del bloque D. main traia una copia paralela del motor del bloque C en los mismos archivos. Co-authored-by: Cursor <cursoragent@cursor.com>
- Updated the `SECURITY.md` to clarify the behavior of journal and snapshots, emphasizing that they are not enterprise-grade backups. - Improved the `preview` functionality for Git operations, ensuring that merge previews do not mutate the working tree and provide detailed conflict detection. - Introduced a new test suite for reset recovery operations, validating the integrity of recovery references and ensuring proper handling of reset scenarios. - Enhanced the `JournalOperaciones` class to support new recovery strategies and maintain journal integrity. - Added utility functions for managing recovery references and detecting merge conflicts in a sandbox environment. This commit aims to improve the reliability and clarity of Git operations within the application, ensuring safer user interactions.
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Fix/conflictos pr 85
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.