`update-data` option still pulls all data

[clayjohn]

Ostensibly update_data should allow you to only retrieve and process the new data for a sub-release instead of pulling the data for every previous sub-release. However, in practice all the data is still fetched from the Github API. Since the process often randomly fails, it would be best if we could avoid those API fetches for partial updates.

As a clear example, today I was updating the changelog for 4.4 dev4. In order to update the changelog for 4.4 dev4, I have to update everything between 4.4dev4 and 4.3 stable. Which means I needed to pull the commit data for over 1200 commits. Each time the process failed after pulling between 300 and 900 commits. Dev4 only had 330 commits, so this should not have been an issue. This issue gets compounded the further into a release we are.

We should be able to avoid those API calls if we have already processed and stored the data locally.

[akien-mga]

Just noting that the option is update-data (kebab-case) and seems to be passed with npm run compose-db version:4.4 update-data.

I confirm that it doesn't seem to do what it seems to be designed for.