Manish Kumar 8b9406ba3e chore: Adding logging mechanism to find out context of redis git locks (#33895) ... ## Description - Introduction of context to redis file locks for git operations. Now the lock would be aware of what command has placed the it. Fixes #`Issue Number` _or_ Fixes `Issue URL` > [!WARNING] > _If no issue exists, please create an issue first, and check with the maintainers if the issue is valid._ ## Automation /ok-to-test tags="@tag.Git" ### 🔍 Cypress test results <!-- This is an auto-generated comment: Cypress test results --> > [!TIP] > 🟢 🟢 🟢 All cypress tests have passed! 🎉 🎉 🎉 > Workflow run: <https://github.com/appsmithorg/appsmith/actions/runs/9318823149> > Commit: 278716d520d9a08e5b39bc24faf770840bf45220 > Cypress dashboard url: <a href="https://internal.appsmith.com/app/cypress-dashboard/rundetails-65890b3c81d7400d08fa9ee5?branch=master&workflowId=9318823149&attempt=1" target="_blank">Click here!</a> <!-- end of auto-generated comment: Cypress test results --> ## Communication Should the DevRel and Marketing teams inform users about this change? - [ ] Yes - [x] No		2024-05-31 20:09:09 +05:30
..
src	chore: Adding logging mechanism to find out context of redis git locks (#33895)	2024-05-31 20:09:09 +05:30
pom.xml	chore(deps): Update BouncyCastle (#33201)	2024-05-07 21:54:48 +05:30