Currently, our db-update action does not trigger automatically when the systems.csv file in the master branch of the gbfs repository is updated. Additionally, there is an opportunity to improve the structure of our database update process by decoupling the updates for GTFS feeds from those for GBFS feeds.
Proposed solution
Adding a trigger that activates the db-update action whenever a merge to the main branch of the gbfs repository includes changes to the systems.csv file. This trigger will ensure that the database is automatically updated with the latest GBFS feed information. Additionally, as part of this improvement, we can explore decoupling the update processes for GTFS and GBFS feeds, allowing for more targeted and efficient database updates.
Describe the problem
Currently, our
db-updateaction does not trigger automatically when thesystems.csvfile in themasterbranch of thegbfsrepository is updated. Additionally, there is an opportunity to improve the structure of our database update process by decoupling the updates for GTFS feeds from those for GBFS feeds.Proposed solution
Adding a trigger that activates the
db-updateaction whenever a merge to themainbranch of thegbfsrepository includes changes to thesystems.csvfile. This trigger will ensure that the database is automatically updated with the latest GBFS feed information. Additionally, as part of this improvement, we can explore decoupling the update processes for GTFS and GBFS feeds, allowing for more targeted and efficient database updates.