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 rely on opening pull to fetch project state and .yaml files from the app to a GitHub repository (as it would when called in a local environment). When this command is called, the latest version of the project (workflows and settings) is fetched and saved in a directory specified in the config.json file.
Whilst this works for most use cases, there's a challenge when openfn pull is triggered by the Sync to GitHub feature on Lightning. This is because there is a lag between when the Sync to GitHub event was triggered and when the GitHub action triggers the openfn pull command. With snapshots, we want to be able to attach a snapshot id to openfn pull so that newer changes are not deployed until the user syncs them by clicking "Sync to GitHub".
The text was updated successfully, but these errors were encountered:
GitHub actions rely on
opening pull
to fetch project state and .yaml files from the app to a GitHub repository (as it would when called in a local environment). When this command is called, the latest version of the project (workflows and settings) is fetched and saved in a directory specified in the config.json file.Whilst this works for most use cases, there's a challenge when openfn pull is triggered by the Sync to GitHub feature on Lightning. This is because there is a lag between when the Sync to GitHub event was triggered and when the GitHub action triggers the
openfn pull
command. With snapshots, we want to be able to attach a snapshot id to openfn pull so that newer changes are not deployed until the user syncs them by clicking "Sync to GitHub".The text was updated successfully, but these errors were encountered: