[Git Sync]: Check if there's a better way to push changes to avoid rate limits

[six7]

Some users report that they're hitting rate limits due to their big number of token sets. When using multi-file sync and you have a lot of token sets, we trigger multiple API calls to GitHub on a push or a pull, even if only 1 file was changed.

Ideally we'd either

• trigger less api calls so that only the changes are pushed that are required instead of every set (which I think is what we do, but still we first check if there's a change)
• or introduce some kind of limiting / slowdown so that we do not run into the problem of rate limits (try creating 300 sets, you'll likely hit a rate limit)

Marking this as a bug as it's causing some users to not be able to push changes if their token sets exceed a certain number.

[JohnathanHuggett]

@six7 Just trying to get some updates on when this bug is going to be worked? This is currently blocking us from using the plugin to update, create, and remove tokens. Thanks!

[UdayHyma]

Migrated to featurebase