-
Notifications
You must be signed in to change notification settings - Fork 26
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
Fetch Project Details Dynamically from GitHub API #177
Comments
@samimshoaib01 try to access http:// not https:// |
@meisabhishekpatel |
@meisabhishekpatel |
@samimshoaib01 ofcourse you need to manage the old design, you need to change in the existing code, not create a new page from scratch . |
@meisabhishekpatel whenever I open the local server using http://127.0.0.1:8000 it shows this I tried using different browsers and disable secure connection option. But still the http changes to https in the browser. Can you help me with this? |
@hexwhiz try incognito or firefox with secure connection off |
@meisabhishekpatel there are some things I want to ask.
|
Also I would like to clarify that do always make API call each time I hit /project instead store the project information in database and new project should be added when I hit populate issues end points then only. |
@meisabhishekpatel PR submitted. And it somehow shows "Review required" with red color. Should I be worried about that? |
@hexwhiz We've added protection to the repository to ensure that no pull request can be merged without proper review and approval. |
Issue Title: Fetch Project Details Dynamically from GitHub API
Description:
Currently, the project information displayed on
/projects
is hardcoded in the HTML template. We want to dynamically fetch project information from the GitHub API to ensure the page stays updated with the latest information.Requirements:
Environment Variables:
PROJECT_NAMES="project1,project2,project3"
Fetch Public Repositories:
Pull Information:
Dynamic Rendering:
Tasks:
/projects
page to display fetched data dynamically.The text was updated successfully, but these errors were encountered: