As discussed in the previous PR, I am planning to close that PR and have raised this one to focus on updating documentation, file paths, and metadata—essentially, all changes that do not require manual updates like tests.

For the test updates, I will raise seven separate PRs, one for each exercise, to ensure clarity and ease of review.

Hi @kahgoh,

This commit syncs the metadata of the Pythagorean Triplet exercise and the instructions.md for the Complex Number exercise, which I recently updated. The PR for the updated instructions.md file has been accepted in the problem-specifications repo.

I wanted to check if contributors typically add their names to the list of authors or contributors when updating an exercise's instructions.md. If not, that’s completely fine—I just want to ensure I’m following the usual practices.

Thanks!

I wanted to check if contributors typically add their names to the list of authors or contributors when updating an exercise's instructions.md. If not, that’s completely fine—I just want to ensure I’m following the usual practices.

I think we normally don't add to the contributors for syncing the instructions.md.

I think we normally don't add to the contributors for syncing the instructions.md.

Hello @kahgoh, I believe there’s been a misunderstanding. I wasn’t referring to syncing the instructions.md. What I meant is that I authored the current introduction.md for the Complex Numbers exercise. My PR was recently accepted in the Problem Specifications repository. So, I wasn’t asking about the syncing process—I’m clarifying that I actually wrote the introduction.md in the Problem Specifications repo. I hope this clears up the confusion.

Hi @jagdish-15, looking at the past precedence (like, for example, in PR #2644, when the leap docs where re-synced after a rewrite) we still normally don't add to the contributors. Adding the contributor (for changes to the Problem Specification) would require the tracks to be aware of the changes to know when to add to the contributor for the exercise across the tracks, which isn't always easy.

Hi @kahgoh,

Thank you for explaining the precedent regarding contributors. I appreciate the insight and completely understand that it might not always be practical to track and add contributors across different tracks for updates originating from the Problem Specifications repository.

I realize I might have been a bit eager in this case, and I truly appreciate your patience in clarifying the usual practices. Moving forward, I'll ensure to align with these norms. Thanks again for your guidance, and I’m glad to have had the opportunity to contribute to the track in any way I can!