To save on API budget; issues found in test/vendored code and instances reported from the loopclosure checker should be saved to disk instead of sending them to GitHub and having TrackBot come along to close the issue later (which was always a hacky approach).
Sticking them on disk keeps the data around while not wasting API calls on things the project plans not to prioritize.
They can always be bulk uploaded to the issue repository after the first pass of crowdsourcing.
kalexmills
commented
3 years ago
To save on API budget; issues found in test/vendored code and instances reported from the loopclosure checker should be saved to disk instead of sending them to GitHub and having TrackBot come along to close the issue later (which was always a hacky approach).
Sticking them on disk keeps the data around while not wasting API calls on things the project plans not to prioritize.
They can always be bulk uploaded to the issue repository after the first pass of crowdsourcing.