You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
But before the front end is implemented, there is a need to create a database table that will store these events. the table will have the same columns as the current table above and rely on the bot automation to save events to the database.
there is a need to find a way to populate the database table with all the previous events. This may call for scrapping the readme table and manually filling the table.
Tools and tech:
MySQL
Node
GitHub API
The text was updated successfully, but these errors were encountered:
I planned to extract the table from the ReadMe to XLX or CSV and write a seeding script to create a table with necessary columns and populate the data to DB.
run the project and sync the database for the new table(events).
run export IMPORT_EVENTS_URL="https://<live-server-address>/api/import-events"
run npm run migrate-events to trigger the bash script and wait for the magic.
this solution can be better if the event is still saved to the ReadME moving forward or we can find a way to auto-save to the database whenever an event badging is completed.
This issue aims at moving the current events table from https://github.com/badging/event-diversity-and-inclusion/blob/main/README.md#badges-granted-version-3 to https://badging.chaoss.community/event-badging
But before the front end is implemented, there is a need to create a database table that will store these events. the table will have the same columns as the current table above and rely on the bot automation to save events to the database.
there is a need to find a way to populate the database table with all the previous events. This may call for scrapping the readme table and manually filling the table.
Tools and tech:
The text was updated successfully, but these errors were encountered: