Hacking on Gitea Actions #246
No reviewers
Labels
No Label
in progress
kind/bug
kind/deployment
kind/docs
kind/enhancement
kind/feature
kind/lint
kind/proposal
kind/question
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
6 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: gitea/blog#246
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "wolfogre/blog:feature/hacking-actions"
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?
English is not my native language, feel free to correct any grammar or tone issues.
It looks like there's something wrong with @website_pr_previewer_bot .
Here is preview page:
http://preview-gitea-org-blog-blog-246.s3-website.eu-central-1.amazonaws.com/2023/03/hacking-on-gitea-actions/
@wolfogre I'll have a look soon WRT to the previewer bot. And I initially thought I did it as "unbreakable" as possible 😓
@wolfogre It looks to me the reason for the comment not to be appearing is that seconds after you opened the PR (and before the drone runner got to it) you posted a comment in the PR.
The CI step essentially looks whether there is already a comment in the PR and if so, skips adding one as it assumes to be the first comment.
So like in this case, if you're adding a comment faster than CI is doing it's first run (instead of editing the content of OP), the comment will not be posted.
Looks good to me generally.
I'd have one question: GitHub actions supports Mac OS and Windows runners too. Is that something that would be possible given a proper setup with the runner on those OS?
It would be nice to finalize changes in the pad before merging.
Done, but removed:
This has been mentioned above and explained later.
@ -0,0 +1,439 @@
---
date: "2023-03-24T14:00:00+08:00"
2023-03-30
lgtm (other than updating the date as delvh mentioned)
@silverwind I added the question
d8026f4ef9
Since I have no way of knowing who made the changes in the pad (I can't identify the users in the change history), please free to add yourself as author.
@silverwind
@delvh
@jolheiser