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
It would be nice if the CLI offered a new command (or perhaps a flag on percy snapshot) that saves the Percy snapshot artifacts into a local directory rather than uploading them. These artifacts could be stored serialized or as png/jpg files etc.
A potential use case for this feature is enabling public repositories to use Percy in their fork PR checks. As percy snapshot requires a Percy token secret, public repos cannot use Percy CLI to take snapshots without allowing contributors to write to their repository directly (GH actions does not expose repository secrets to forks on pull_request triggers). With this change, public repos could have a fork pull_request action take percy snapshots and archive them as a build artifact, enabling the base repo to call percy upload on those screenshot artifacts.
The text was updated successfully, but these errors were encountered:
Similar issue: #1327
It would be nice if the CLI offered a new command (or perhaps a flag on
percy snapshot
) that saves the Percy snapshot artifacts into a local directory rather than uploading them. These artifacts could be stored serialized or as png/jpg files etc.A potential use case for this feature is enabling public repositories to use Percy in their fork PR checks. As
percy snapshot
requires a Percy token secret, public repos cannot use Percy CLI to take snapshots without allowing contributors to write to their repository directly (GH actions does not expose repository secrets to forks onpull_request
triggers). With this change, public repos could have a forkpull_request
action take percy snapshots and archive them as a build artifact, enabling the base repo to callpercy upload
on those screenshot artifacts.The text was updated successfully, but these errors were encountered: