-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Trigg event action from WebUI #2139
Labels
issue/confirmed
Issue has been reviewed and confirmed to be present or accepted to be implemented
type/enhancement
An improvement of existing functionality
Comments
You can do that via webhooks |
Hi
How ? documentation about webhook is empty
https://docs.gitea.io/en-us/webhooks/
|
see #2418 to find the webhooks works. |
maybe you mean #1663 |
Hello
I'm not sure is exactly same.
I think about actions as "move repository". I check github api to have an
idea but I don't found this action. Maybe can be considered as two action
create and delete.
Other aspect in my mind with this question, action trigged could be
related to local hosting (as to add hook configuration). But i think this
aspect could be workarounded with webhook.
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions. |
Need repository transfered webhook. |
lunny
added
the
issue/confirmed
Issue has been reviewed and confirmed to be present or accepted to be implemented
label
Feb 13, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
issue/confirmed
Issue has been reviewed and confirmed to be present or accepted to be implemented
type/enhancement
An improvement of existing functionality
Hi
Should be possible to trigg event/action from WebUI.
I've an use case where I need to detect when a repository is created/moved to/from a specific organization.
I need to execute a script to add new repo on our workflow
On another use case should be trigg user creation to set it on different team.
The text was updated successfully, but these errors were encountered: