Update check_git_status() to run under ROOT working directory

[MrinalJain17]

Fixes #5440

🛠️ PR Summary

_{Made with ❤️ by Ultralytics Actions}

🌟 Summary

New context manager for changing working directory in code sections.

📊 Key Changes

• Introduced a new class WorkingDirectory as a context manager to change the current working directory within a code block.
• The @WorkingDirectory(ROOT) decorator has been applied to the check_git_status function.

🎯 Purpose & Impact

• 🎯 Purpose: This change allows developers to seamlessly change the working directory while executing certain functions or code blocks, improving code organization and keeping file path references relative and consistent.
• 💥 Impact: Users can expect more reliable file handling when the script changes directories, potentially reducing file path errors. Additionally, the developers can use this functionality to ensure that certain functions always run in the same directory context, which is especially helpful for maintaining relative paths.

[github-actions]

👋 Hello @MrinalJain17, thank you for submitting a 🚀 PR! To allow your work to be integrated as seamlessly as possible, we advise you to:

• ✅ Verify your PR is up-to-date with upstream/master. If your PR is behind upstream/master an automatic GitHub actions rebase may be attempted by including the /rebase command in a comment body, or by running the following code, replacing 'feature' with the name of your local branch:

git remote add upstream https://github.com/ultralytics/yolov5.git
git fetch upstream
git checkout feature  # <----- replace 'feature' with local branch name
git merge upstream/master
git push -u origin -f

• ✅ Verify all Continuous Integration (CI) checks are passing.
• ✅ Reduce changes to the absolute minimum required for your bug fix or feature addition. "It is not daily increase but daily decrease, hack away the unessential. The closer to the source, the less wastage there is." -Bruce Lee

[MrinalJain17]

@glenn-jocher This PR fixes the issue raised in #5440 . Let me know if you have any thoughts on this.

[glenn-jocher]

@MrinalJain17 this is a nice solution! I like the context manager approach.

My main question here is would it be possible to pass a directory argument to the context manager to generalize it's capability? i.e. something like:

with ChangeWorkingDirectory(dir=ROOT):
    # do stuff

[MrinalJain17]

My main question here is would it be possible to pass a directory argument to the context manager to generalize it's capability? i.e. something like:

@glenn-jocher That makes sense. Updated the PR accordingly.

I didn't set a default value within the context manager to avoid any unintended change in the working directory. The user has to explicitly specify the directory to which it should switch.

[glenn-jocher]

@MrinalJain17 PR is merged. Thank you for your contributions to YOLOv5 🚀 and Vision AI ⭐