@AurumnPegasus can you please help me fix test cases

The issue does not seem to be in the code (atleast for now, will know more when those tests are executed) but from code quality.
Ensure that you have followed instructions for dev installation as mentioned in the guide

Once you have done that, ensure you run pre-commit when you stage files for changes (BEFORE committing anything). Once the pre-commit tests pass, then commit your changes and push them to your branch.

In my opinion, I think you are skipping the pre-commit step, so let me know if it resolves your blocker

@nilesh05apr, as @AurumnPegasus said, you need to follow code formatting standards. How-to is outlined on this developer page:
https://www.sktime.org/en/stable/developer_guide/coding_standards.html

For quick inspection, you can also check the "details" next to the failed CI element "Install and test / code-quality (pull_request)"

Hey @nilesh05apr, do you still want to work on this? I'd had users ask me when this would be available in sktime and since you're almost done I wanted to nudge you regarding it.

I'll be happy to extend any support to you if required.

Thanks.

@achieveordie thanks for asking. I am working on it, but some tests are failing. let me try if it's not so urgent.

Absolutely!

Solving the failure due to code-quality check is actually very trivial. As per this comment on this thread, you need to set up your dev setup properly.

Once you've done that you can make any slight change (like an additional space in the docstring) in your PR and commit it. pre-commit will then run and help you rectify problems relating to code formatting.

PS: I'd recommend resolving conflicts first.

@achieveordie , @AurumnPegasus i have added new pr as old one got clumsy.
please check test results for fix: pre-commit errors #3881