You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In our current usage of LakeFS, we have several highly monitored repositories where we rely on hooks to validate dataset integrity.
Pre-commit hooks allow us to run quick validation steps before commits.
Post-merge hooks help enforce compliance with more complex rules and index datasets.
By combining protected branches with these hooks, we ensure that any commits to Main (or other protected branches) undergo strict validation.
However, we noticed that reverting a commit does not trigger any hooks—neither pre-revert nor post-revert. As a result, a user can revert a commit on a branch without any validation, making it difficult to track the real status of the repository.
Would it be possible to extend the supported events list to include a revert event? This would allow us to monitor and enforce rules on revert operations as well.
Thanks a lot!
The text was updated successfully, but these errors were encountered:
Hello,
In our current usage of LakeFS, we have several highly monitored repositories where we rely on hooks to validate dataset integrity.
By combining protected branches with these hooks, we ensure that any commits to Main (or other protected branches) undergo strict validation.
However, we noticed that reverting a commit does not trigger any hooks—neither pre-revert nor post-revert. As a result, a user can revert a commit on a branch without any validation, making it difficult to track the real status of the repository.
Would it be possible to extend the supported events list to include a revert event? This would allow us to monitor and enforce rules on revert operations as well.
Thanks a lot!
The text was updated successfully, but these errors were encountered: