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
As I said in this comment, the current logic for notifications is imperfect in that they trigger when the site deploys with a change to the HTML rather than a change to the underlying data.
I'm not really sure how we could distinguish the two, honestly. We could hack around it by creating a separate file to track just the data that'd be updated every time the data updates (and then check for updates to that file rather than the generated HTML), or change the commit message when it is/isn't a data update.
The text was updated successfully, but these errors were encountered:
As I said in this comment, the current logic for notifications is imperfect in that they trigger when the site deploys with a change to the HTML rather than a change to the underlying data.
I'm not really sure how we could distinguish the two, honestly. We could hack around it by creating a separate file to track just the data that'd be updated every time the data updates (and then check for updates to that file rather than the generated HTML), or change the commit message when it is/isn't a data update.
The text was updated successfully, but these errors were encountered: