Upload snapshot in LGTM specification
A documented LGTM specification operation that changes something in your account. Describe the outcome you want in plain words — HumDay writes the program, proves it, and runs it.
What this operation does
Upload snapshot
- PUTChanges data · Snapshots
lgtm.com/snapshots/uploads/{session-id}
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which LGTM specification operations the program may use, and this is one of them.
- You approve access. Because this one changes data, it cannot run until you have explicitly granted it.
Other LGTM specification operations
- Add a project to LGTMPOST · changes data
- Run a CodeQL query on one or more projectsPOST · changes data
- Abort database upload processDELETE · changes data
- Complete snapshot upload sessionPOST · changes data
- Start snapshot upload sessionPOST · changes data
- Run analysis of a specific commitPOST · changes data
- Delete project by numeric identifierDELETE · changes data
- Run code review for a patchPOST · changes data
Questions
- Can HumDay upload snapshot in LGTM specification?
- Yes. This operation is published in LGTM specification's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
- Will this change my LGTM specification data?
- Yes — this is a PUT operation, so it changes something in LGTM specification. HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.
- Do I need to write code?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your LGTM specification account.
Where this came from
Read from a published API description for LGTM specification at lgtm.com/api/v1.0/openapi. The description above is the provider’s own wording, not ours. Last published 2021-06-21.