-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Output gbfs-validator version in the HTTP API response #77
Comments
@PierrickP Just checking, at the moment is it possible to rely on the commit SHA on |
PierrickP
added a commit
that referenced
this issue
Aug 19, 2022
Return git hash on netlify, based on COMMIT_REF env variable or package.json's version Close #77
PierrickP
added a commit
that referenced
this issue
Aug 19, 2022
Return git hash on netlify, based on COMMIT_REF env variable or package.json's version Close #77
PierrickP
added a commit
that referenced
this issue
Aug 19, 2022
Return git hash on netlify, based on COMMIT_REF env variable or package.json's version Close #77
PierrickP
added a commit
that referenced
this issue
Aug 19, 2022
Return git hash on netlify, based on COMMIT_REF env variable or package.json's version Close #77
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is a suggestion for an enhancement.
It would be helpful to be able to know the version of the gbfs-validator used when validating a GBFS feed. As this repository evolves, it seems like a good idea to store the specific version used to validate a feed.
Maybe add a field in the
summary
or add a newmeta
field?Sample response
The text was updated successfully, but these errors were encountered: