Debugging setup of VS Code section update

[mustious]

Signed-off-by: Mustapha Abdullahi mustious@gmail.com

Description

The earlier documentation will give some users difficulty in setting up VS Code debugging with Kedro as there has been changes in VS Code UI. This PR provides a more descriptive guide to the users in setting up debugging. Following this commit (focused on the debugging), more updates will be made on the overall Kedro with VS Code setup documentation to reflect changes of VS Code UI.

Development notes

Only documentation markdown changed.

Developer Certificate of Origin

We need all contributions to comply with the Developer Certificate of Origin (DCO). All commits must be signed off by including a Signed-off-by line in the commit message. See our wiki for guidance.

If your PR is blocked due to unsigned commits, then you must follow the instructions under "Rebase the branch" on the GitHub Checks page for your PR. This will retroactively add the sign-off to all unsigned commits and allow the DCO check to pass.

Checklist

• Read the contributing guidelines
• Signed off each commit with a Developer Certificate of Origin (DCO)
• Opened this PR as a 'Draft Pull Request' if it is work-in-progress
• Updated the documentation to reflect the code changes
• Added a description of this change in the RELEASE.md file
• Added tests to cover my changes
• Checked if this change will affect Kedro-Viz, and if so, communicated that with the Viz team

[astrojuanlu]

RTD failure seems unrelated: https://beta.readthedocs.org/projects/kedro/builds/22239120/#206508356--366

[astrojuanlu]

Thanks for your PR @mustious! I left a comment

[astrojuanlu]

Instructions look OK to me! Paging @stichbury for the final review

[astrojuanlu]

The DCO bot is failing because commit authorship email does not match signoff email, @mustious do you mind having a look at that? You did right by signing off the commits with -s, but I think you have your personal email configured globally for git (you can check by doing git config --get-all user.email).

[mustious]

The DCO bot is failing because commit authorship email does not match signoff email, @mustious do you mind having a look at that? You did right by signing off the commits with -s, but I think you have your personal email configured globally for git (you can check by doing git config --get-all user.email).

Yes very true. I was using a QB email in my git and a personal email in signing-off. I will make the necessary changes. Thank you @astrojuanlu

[stichbury]

Requested changes noted in comment on the file

[stichbury]

LGTM thanks @mustious ! 🌟

[astrojuanlu]

(I'm meeting with @mustious next week to see if we can understand what's going on with the signoff 😄)

[mustious]

(I'm meeting with @mustious next week to see if we can understand what's going on with the signoff 😄)

Thanks so much @astrojuanlu for your assistance 🚀🎉

[astrojuanlu]

RTD problem is unrelated:

sphinx.errors.SphinxWarning: /home/docs/checkouts/readthedocs.org/user_builds/kedro/checkouts/3181/docs/source/nodes_and_pipelines/pipeline_registry.md:34:broken link: https://github.com/kedro-org/kedro-starters/blob/main/spaceflights/%7B%7B%20cookiecutter.repo_name%20%7D%7D/src/%7B%7B%20cookiecutter.python_package%20%7D%7D/pipeline_registry.py (404 Client Error: Not Found for url: https://github.com/kedro-org/kedro-starters/blob/main/spaceflights/%7B%7B%20cookiecutter.repo_name%20%7D%7D/src/%7B%7B%20cookiecutter.python_package%20%7D%7D/pipeline_registry.py)

We will fix it separately