Currently I'm leveraging a very janky {cache} and {variables} to cache the results returned from GitHub's API so we're not sending requests all the time.
In order to facilitate the future "releases" we should really store these in their own table so we can associate more Drupal/site specific information along side them.
Currently I'm leveraging a very janky
{cache}and{variables}to cache the results returned from GitHub's API so we're not sending requests all the time.In order to facilitate the future "releases" we should really store these in their own table so we can associate more Drupal/site specific information along side them.
ref: #6, #9