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
Initially, content will only get pulled into the database from the GitHub repo. We'll need to define a task that pulls content in whenever the main branch is updated (this could run from a webhook).
Less important: would it be possible to report progress/success through the github api? (the way that vercel/netlify deploys work)
Ideally, it should be possible to track the most recent change applied so that the task only needs to check for new commits and replace any records that have been modified. (e.g. a single edit to one post doesn't involve updating the db for every post on the site)
It will (in the future) be necessary to write updates made in the db back to the github repo as well. However, that is not an immediate goal.
The text was updated successfully, but these errors were encountered:
Initially, content will only get pulled into the database from the GitHub repo. We'll need to define a task that pulls content in whenever the
main
branch is updated (this could run from a webhook).Less important: would it be possible to report progress/success through the github api? (the way that vercel/netlify deploys work)
Ideally, it should be possible to track the most recent change applied so that the task only needs to check for new commits and replace any records that have been modified. (e.g. a single edit to one post doesn't involve updating the db for every post on the site)
It will (in the future) be necessary to write updates made in the db back to the github repo as well. However, that is not an immediate goal.
The text was updated successfully, but these errors were encountered: