Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question regarding gh_url mixed with latest and first release manual data #233

Closed
MattTheCuber opened this issue Dec 24, 2024 · 3 comments · Fixed by #227
Closed

Question regarding gh_url mixed with latest and first release manual data #233

MattTheCuber opened this issue Dec 24, 2024 · 3 comments · Fixed by #227

Comments

@MattTheCuber
Copy link
Contributor

Specifically rand, it has gh_url and manual keys (e.g. latest_release_version). Is this a mistake?

@MattTheCuber
Copy link
Contributor Author

Also, what's the difference between _gh_url and repo_url. I know that neither are used, but do they mean the same thing?

@mahmoud
Copy link
Owner

mahmoud commented Dec 24, 2024

I think sometimes I had to do manual keys for when the github tags weren't there. As for the key names, unlike Awesome Python Applications there's no schema. I was going with something self-documenting. If the repo is on github, it could easily be a gh_url or _gh_url.

I've been wanting to write an apatite-like command that'll validate and clean up the yaml. Specifically, all the alumni could have their attributes frozen into the yaml so as to speed up update time.

@mahmoud
Copy link
Owner

mahmoud commented Dec 24, 2024

Not sure if you've tried running gen_projects_json.py yet, but the local command I use is just:

GH_USER=mahmoud GH_TOKEN=$(cat /path/to/github_token.txt) python tools/gen_projects_json.py

The project does not need any requirements outside of what chert uses, so you can create a virtualenv from the requirements.txt over there. Python 3.10 is tested working.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants