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
I would like to setup a workflow that can be triggered from a separate repository to then pull the content of that repository, build stuff with it and push it to the own repo's gh-pages branch under a specific folder.
Looking into this action, I can see it has an option to set a remote target repo, but not a remote source repo... So I was wondering: If I would use action/checkout's feature of defining a remote repository as source, would this action here use that repo as the source instead of the local one?
And if not, can it be considered to add an option to define a remote repository as the source?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I would like to setup a workflow that can be triggered from a separate repository to then pull the content of that repository, build stuff with it and push it to the own repo's gh-pages branch under a specific folder.
Looking into this action, I can see it has an option to set a remote target repo, but not a remote source repo... So I was wondering: If I would use action/checkout's feature of defining a remote repository as source, would this action here use that repo as the source instead of the local one?
And if not, can it be considered to add an option to define a remote repository as the source?
Beta Was this translation helpful? Give feedback.
All reactions