Update README.md

[lohith1511]

except python, the tables format aligned neatly.

[drkrillo]

Problem

You are modifying README.md, which solves the probelm temporaly. Let me explain what I mean:

1. a githubactions workflow runs every day to re-render README.md
2. this workflow triggers update_issues.py, which uses README.md.j2 template, inside app/templates/
3. then, this re-rendered README.md is published in the main entry of the repository.

With your actual solution, the problem will be solved but just for that day's README file. Next day, when update_issues.py is run again by the githubactions workflow, the problem will persist.

Solution

Instead of modifying README.md, which is only a temporal solution, you should solve the problem from the root cause: the template itself, app/templates/README.md.j2.

1. Inside this file, there is a template to render the tables by programming language.
2. The problem is in this section:

{% for result in results -%}
### {{result.language}}

| Repo | Title | Comments |
| --- | --- | --- |

{% for issue in result.issues -%}
| {{issue.repo}} | [{{issue.title}}]({{issue.url}}) | {{issue.comments}} |
{% endfor %}
{% endfor %}

3. The table is not rendering correctly the issues: instead of creating a table for them, is creating a string with the | symbol concatenating them, but not showing them in a table format, which suggests that the formatting for the table is not correct.

That formatting should be solved.

It shouldn't be a big PR, maybe just a line or two of difference.

[drkrillo]

In case you need guidance to:

1. running the project locally
2. creating a github API access token
3. setting the environment variables so that you have all set up locally to run the project,

Just let me know and we can find a way to talk about it in a more in-depth manner.

[drkrillo]

Are you still working on this? @lohith1511

[lohith1511]

No I am working on other repo’s.

…

On Thu, Mar 20, 2025 at 8:00 PM drkrillo ***@***.***> wrote: Are you still working on this? @lohith1511 <https://github.com/lohith1511> — Reply to this email directly, view it on GitHub <#47 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BEJV7C7XZHONW2LFHOF6OZD2VLGIBAVCNFSM6AAAAABXPCDLS6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONBQGY2TIMRRGU> . You are receiving this because you were mentioned.Message ID: ***@***.***> [image: drkrillo]*drkrillo* left a comment (drkrillo/good-first-issues#47) <#47 (comment)> Are you still working on this? @lohith1511 <https://github.com/lohith1511> — Reply to this email directly, view it on GitHub <#47 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BEJV7C7XZHONW2LFHOF6OZD2VLGIBAVCNFSM6AAAAABXPCDLS6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONBQGY2TIMRRGU> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[AbiRaja-tech]

@drkrillo @P3st83 Hey I can still see the table is having same issue and would love to resolve it. Please let me know if I can proceed with it.
XD:)

[drkrillo]

@AbiRaja-tech hi there. Sorry for my delay.

You can try to solve it. The problem is in the template, not the README.

Feel free to try out :)