MAINTAINERS.json is used to attach assignees to automatically-generated PRs
some small tweaks have been made to src/snippet.js but prior changes were reviewed by @bddean
Etc.
I'm currently using a fake snippet service as part of the workflow. There is a separate arc of work afoot that will build the real endpoint. Once done, the GH Action workflow config will need to be updated with the proper endpoint.
GitHub Actions execute from master, which is why I needed to clone the fullstorydev/fullstory-browser-sdk repo into my own account to build the action (no branch restrictions on master there).
Hello! The first draft of GitHub Actions for synchronizing snippets is ready.
The use case for this PR is here: https://github.com/fullstorydev/fullstory-browser-sdk/issues/14
3 test scenarios
(Using the GitHub Action results on my fork: https://github.com/patrick-fs/fullstory-browser-sdk)
Review the output of the
Sync snippet
step:Files of particular importance
.github/workflows/main.yml
defines the Action workflow.github/actions/sync-snippet-action/main.js
is the script that executes syncronizationMAINTAINERS.json
is used to attach assignees to automatically-generated PRssrc/snippet.js
but prior changes were reviewed by @bddeanEtc.
master
, which is why I needed to clone thefullstorydev/fullstory-browser-sdk
repo into my own account to build the action (no branch restrictions onmaster
there).Cc
@jameremo @marktisham