You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we are using numbered revisions for the resource index JSON, e.g. resources/v1.json.gz.
This means devs have to be cognizant of when to bump the revision number and there's also potential for revision number clashes between WIP branches and PRs.
Past discussion floated the idea of using commit ids as the version of the resource index, but leaving this as future decision.
The text was updated successfully, but these errors were encountered:
Context
Currently we are using numbered revisions for the resource index JSON, e.g.
resources/v1.json.gz
.This means devs have to be cognizant of when to bump the revision number and there's also potential for revision number clashes between WIP branches and PRs.
Past discussion floated the idea of using commit ids as the version of the resource index, but leaving this as future decision.
The text was updated successfully, but these errors were encountered: