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
We trigger an update, so the editor will trigger the hook and will call the pipeline again.
So we might have to update the status to indicate that the pipeline has processed it.
Or we have to use the 'user' parameter to see if the update was caused by the pipeline, if that is possible?
The text was updated successfully, but these errors were encountered:
@ekoi is working on making it possible to use the API token for the "protected" API, that token will map to the default user (app specific or global). If we add users to the editor you can see if the hook was triggered by the default user (API token) or an editor (basic auth for now)
We trigger an update, so the editor will trigger the hook and will call the pipeline again.
So we might have to update the status to indicate that the pipeline has processed it.
Or we have to use the 'user' parameter to see if the update was caused by the pipeline, if that is possible?
The text was updated successfully, but these errors were encountered: