Skip to content
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

Fix Organization Webhook to Trigger when something is forked into it #169

Closed
jag3773 opened this issue May 2, 2017 · 3 comments
Closed
Assignees

Comments

@jag3773
Copy link
Contributor

jag3773 commented May 2, 2017

Story

As a developer I want the organization's webhook to fire when a new repo is forked into said organization so that I know something changed and can use the data.

Scenario: User_A likes My_Cool_Repo and forks it into Org_A, the webhook fires and and everyone is happy.

Our Scenario: We receive a source text request which we fulfill by forking the source repository into our Door43-Catalog repository, which fires the webhook and starts an update of our API v3 catalog.

@jag3773 jag3773 added the Gogs label May 2, 2017
@ethantkoenig
Copy link
Contributor

Right now, the only supported webhook events are

  • "create": when a branch or tag is created
  • "push": push to a repository
  • "pull": pull request opened, closed, reopened, edited, assigned, unassigned, label updated, label cleared, or synchronized

I've created a PR upstream (go-gitea/gitea#1663) to support webhooks for "repository" events (repository created or deleted in an org). An organization forking a repository is just a special case of the "repository" event.

If there are any other webhooks events you need implemented, let me know. Github, for instance, supports a fairly comprehensive set of events (https://developer.github.com/webhooks/#events)

@ethantkoenig
Copy link
Contributor

@jag3773. This webhook was implemented in go-gitea/gitea#1663, which was included in the 1.4.0 release. Is it not working as expected?

@jag3773
Copy link
Contributor Author

jag3773 commented Jan 22, 2018

I haven't tried, which is why I stuck that label on it. Can you verify that this is working?

@jag3773 jag3773 closed this as completed Feb 9, 2018
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 24, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants