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
Not an issue, but some clarifying questions to a new user:
Why does remote_name default to deploy as opposed to origin?
why does branch default to master as opposed to whatever branch is currently checked out (ie ${DRONE_BRANCH})?
ssh_key is mandatory right, ie. there's no way to tap into the authentication granted to drone instance itself?
why doesn't remote default to ${DRONE_GIT_SSH_URL}?
This is so the pipeline step definition could be less verbose, assuming the most common use-case would be (commiting and) pushing back to same reporitory & branch.
Following drone step definition works, but feels like it could/should be more terse:
Not an issue, but some clarifying questions to a new user:
remote_name
default todeploy
as opposed toorigin
?branch
default tomaster
as opposed to whatever branch is currently checked out (ie${DRONE_BRANCH}
)?ssh_key
is mandatory right, ie. there's no way to tap into the authentication granted to drone instance itself?remote
default to${DRONE_GIT_SSH_URL}
?This is so the pipeline step definition could be less verbose, assuming the most common use-case would be (commiting and) pushing back to same reporitory & branch.
Following drone step definition works, but feels like it could/should be more terse:
The text was updated successfully, but these errors were encountered: