ci: update git push action for secure authentication #162
No reviewers
Labels
No Label
in progress
kind/bug
kind/deployment
kind/docs
kind/enhancement
kind/feature
kind/lint
kind/proposal
kind/question
kind/refactor
kind/security
kind/testing
kind/translation
kind/ui
lgtm/done
lgtm/need 1
lgtm/need 2
priority/critical
priority/low
priority/maybe
priority/medium
reviewed/duplicate
reviewed/invalid
reviewed/wontfix
status/blocked
status/needs-feedback
status/wip
No Milestone
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: gitea/homebrew-gitea#162
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "appleboy/homebrew-gitea:appleboy-patch-1"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Signed-off-by: appleboy appleboy.tw@gmail.com
@ -22,0 +20,4 @@
branch: main
commit: true
commit_message: "[skip ci] Updated Version via cron"
remote: "git@gitea.com:gitea/act_runner.git"
Why push to act_runner?
I have my doubts about replacing a flexible and easily understandable series git commands with an additional abstraction layer that may have its own weird behaviours and which requires every contributor to learn it, vs. git which is much more common knowledge.
BTW, the git commands will use the action context
gitea.token
for authentication, so they do not require an additional secret as deploy key.