Currently, users register their packages by submitting a PR to the new-packages.json file in this repository. However, they can also register their packages via the registry API using GitHub Issues. If they do so, then the legacy registry files in this repository won't be updated -- they aren't kept in sync.
This PR remedies this issue by synchronizing with the new-packages and bower-packages files in this repository when an addition or transfer happens.
This is also a step towards migrating the legacy registry files into the registry proper, and disabling pull requests, so that all registrations happen via the registry API (which provides feedback in case the registration fails, unlike the PR to the legacy files).
Currently, users register their packages by submitting a PR to the
new-packages.jsonfile in this repository. However, they can also register their packages via the registry API using GitHub Issues. If they do so, then the legacy registry files in this repository won't be updated -- they aren't kept in sync.This PR remedies this issue by synchronizing with the new-packages and bower-packages files in this repository when an addition or transfer happens.
This is also a step towards migrating the legacy registry files into the registry proper, and disabling pull requests, so that all registrations happen via the registry API (which provides feedback in case the registration fails, unlike the PR to the legacy files).