gitea/awesome-gitea
56
137
Fork 88
Code Issues 2 Pull Requests Actions Releases Activity

Add Gitea Actions link #76

Closed
asriel wants to merge 1 commits from asriel/awesome-gitea:master into main
pull from: asriel/awesome-gitea:master
merge into: gitea:main
Conversation 6 Commits 1 Files Changed 1 +1
asriel commented 2022-05-01 08:14:08 +00:00
First-time contributor
Copy Link

Made this little script to add GitHub Actions integration into Gitea's API. I figured it'd be useful for others, so I wanted to add a link to it here. If you have any gripes with it, I can improve the implementation if need be.

Example Screenshot

Made this little script to add GitHub Actions integration into Gitea's API. I figured it'd be useful for others, so I wanted to add a link to it here. If you have any gripes with it, I can improve the implementation if need be. ![Example Screenshot](/attachments/87827789-b429-45c4-9d03-60ed1629e201)
image.png
20 KiB
asriel added 1 commit 2022-05-01 08:14:09 +00:00
lunny commented 2022-05-01 08:41:11 +00:00
Owner
Copy Link

I have reviewed the python script but don't know how it works.

I have reviewed the python script but don't know how it works.
asriel commented 2022-05-01 09:33:36 +00:00
Author
First-time contributor
Copy Link

Yeah, it might be best to accompany it with a list of instructions perhaps?

That python script is to run in the background as a daemon, and I provide a simple systemd .service file that I use. To set it up, you create a webhook for your repository pointing to the http server, and check the workflow jobs box to have the webhook only trigger for workflows/actions. When a new workflow is run, the server recieves the webhook and sends the appropriate API call to the Gitea repo.

Yeah, it might be best to accompany it with a list of instructions perhaps? That python script is to run in the background as a daemon, and I provide a simple systemd .service file that I use. To set it up, you create a webhook for your repository pointing to the http server, and check the workflow jobs box to have the webhook only trigger for workflows/actions. When a new workflow is run, the server recieves the webhook and sends the appropriate API call to the Gitea repo.
jolheiser commented 2022-05-01 19:18:13 +00:00
Owner
Copy Link

So is this used in conjunction with a push mirror?

Do you have an example of this running somewhere publicly?
I'm fairly sure I know how it works, but not sure what kicks it off, since this seems to originate from GitHub and this script essentially mirrors the status over to a Gitea instance.

So is this used in conjunction with a push mirror? Do you have an example of this running somewhere publicly? I'm fairly sure I know how it works, but not sure what kicks it off, since this seems to originate from GitHub and this script essentially mirrors the status over to a Gitea instance.
asriel commented 2022-05-01 21:18:07 +00:00
Author
First-time contributor
Copy Link

Yep, I use a push mirror in order to have GitHub actually recieve the commits. You can see me using it on Gitea here and on GitHub here.

Yep, I use a push mirror in order to have GitHub actually recieve the commits. You can see me using it on Gitea [here](https://git.camora.dev/asriel/L4) and on GitHub [here](https://github.com/WorkingRobot/L4).
6543 commented 2022-05-01 21:30:08 +00:00
Owner
Copy Link

@asriel I think this should not be a gist but a repo with a Readme that explain how to setup :)

@asriel I think this should not be a gist but a repo with a Readme that explain how to setup :)
6543 commented 2023-03-21 02:56:15 +00:00
Owner
Copy Link

name would collide with gitea feature ...

name would collide with gitea feature ...
6543 closed this pull request 2023-03-21 02:56:15 +00:00

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Assignees
Clear assignees
No Assignees
4 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: gitea/awesome-gitea#76
No description provided.
Delete Branch "asriel/awesome-gitea:master"

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?