update track-first-steps-progress.md (fixes #3585)

[munishpatel]

Important: Do not tick a checkbox if you haven’t performed its action.

Before Creating the Pull Request

• Verify the changes are on a new branch other than master – it should say "compare: branch-name".
• Start the pull request title with lowercase letters, e.g., add githubusername.md.
• Add issue number to the end of the pull request title when applicable, e.g., update mi-faq.md (fixes #3264).

After Creating the Pull Request

• Go to "Commits" tab, make sure the commit username is clickable and linked to your GitHub account correctly.
• Review the "Files changed" tab to ensure there are no unnecessary files or changes included in the pull request.
• Verify that the raw.githack preview link is included in the description.
  • Preview the MDwiki rendered changes using the raw.githack link. Ensure it displays as expected without any errors.
• Drop a link to this pull request in our discord channel.

Description, Screenshots and/or Screencast

<--Made changes in the code for track-first-steps-progress.md file for creating the comments count. -->

fixes #3585

Raw.Githack Preview Link

<-- https://raw.githack.com/munishpatel/munishpatel.github.io/3585-add-comments-count/index.html#!pages/track-first-steps-progress.md -->

[jessewashburn]

I'm not able to see the comments count in your raw githack.link. Please advise if I'm doing something wrong (note this output is for @Mutugi who should definitely have some comments to count). Feel free to provide your own screenshot.

[munishpatel]

I have made the required changes @jessewashburn . In the track-first-step-progress.md file we need to add a access token to access the Github's API. The below is the placeholder for the access token for your reference:

I executed the application using my personal access code, the below is the screenshot for your reference:

[jessewashburn]

Can you tell me what kind of output your getting for 'Mutugiii'? Mine is showing 0 comments, which isn't right.

Also, can you manually verify that the 4 comments it's counting for you is an accurate count? I'm not sure.

[munishpatel]

I guess that's because the function is checking the issues which are in "OPEN" state.
While checking the 'Mutugiii' tracking process, I am getting an rate limit exceeded error in my api call.
After checking manually I have 4 comments on the issues.

[Sakshamnayyar]

If you're running into API rate limits, it might be better to limit the check to a specific number of recent issues, maybe around 20 to 50. We'd need to experiment a bit to find this number. Also, it would be helpful to mention this limit in the progress tracker UI so users know its based on recent issues, not full repo.