Skip to content

fix: devices routes wrong path parameter and 403 instead of 404 response #21

fix: devices routes wrong path parameter and 403 instead of 404 response

fix: devices routes wrong path parameter and 403 instead of 404 response #21

Triggered via pull request April 14, 2024 09:55
@flxdotflxdot
opened #22
Status Success
Total duration 11s
Artifacts

pr-assign-author.yml

on: pull_request_target
assign-author
4s
assign-author
Fit to window
Zoom out
Zoom in