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
GitHub actions should generate side-by-side images of PR changes, for example:
Sample Name
Before
After
historic_us66_oklahoma
For demonstration purposes, the banner on the Historic US 66 shield has been changed to a nonsense value. Also note for the real implementation, I intend to include the attribution notice in the sample clip as there's a strong likelihood that they get copied around.
Design:
The repository will hold a configuration file which contains a list of "interesting" locations which will be used by a GitHub action to generate screenshots of that location on the map. The action will generate screenshots for both the main branch and the PR branch and collect a set of images which have differences between the two branches. The action will use the PR version of the screenshot configuration so that it's the same one-to-one comparison.
Then, only those locations which have differences will be added to the "PR Preview" check after the existing content:
Process Changes:
Once we have this functionality in place, we should encourage PR creators to add sample locations to the file when new features are added. This will help us visually catch regressions in future PRs and simplify the process of showing changes. I anticipate adding instructions to this effect in our contributor guide.
Implementation:
#942 and #945 added the ability to render samples from a script, at the command line. I intend to use this functionality along with additional scripting to run the comparisons and update the appropriate GitHub action. Since this will require changes to the "privileged" GitHub action, a portion of the implementation will need to include un-previewable changes to main that I will commit separate from the in-progress PR #956 that's implementing this capability.
I'm looking for concurrence on this approach given that I'll need to push a change to main to enable the changes to the privileged action script.
The text was updated successfully, but these errors were encountered:
Proposal:
GitHub actions should generate side-by-side images of PR changes, for example:
For demonstration purposes, the banner on the Historic US 66 shield has been changed to a nonsense value. Also note for the real implementation, I intend to include the attribution notice in the sample clip as there's a strong likelihood that they get copied around.
Design:
The repository will hold a configuration file which contains a list of "interesting" locations which will be used by a GitHub action to generate screenshots of that location on the map. The action will generate screenshots for both the main branch and the PR branch and collect a set of images which have differences between the two branches. The action will use the PR version of the screenshot configuration so that it's the same one-to-one comparison.
Then, only those locations which have differences will be added to the "PR Preview" check after the existing content:
Process Changes:
Once we have this functionality in place, we should encourage PR creators to add sample locations to the file when new features are added. This will help us visually catch regressions in future PRs and simplify the process of showing changes. I anticipate adding instructions to this effect in our contributor guide.
Implementation:
#942 and #945 added the ability to render samples from a script, at the command line. I intend to use this functionality along with additional scripting to run the comparisons and update the appropriate GitHub action. Since this will require changes to the "privileged" GitHub action, a portion of the implementation will need to include un-previewable changes to main that I will commit separate from the in-progress PR #956 that's implementing this capability.
I'm looking for concurrence on this approach given that I'll need to push a change to main to enable the changes to the privileged action script.
The text was updated successfully, but these errors were encountered: