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

Implement Codebase webhook using the Event Hook API #9395

Open
eeshangarg opened this issue May 15, 2018 · 20 comments · May be fixed by #12260
Open

Implement Codebase webhook using the Event Hook API #9395

eeshangarg opened this issue May 15, 2018 · 20 comments · May be fixed by #12260

Comments

@eeshangarg
Copy link
Member

We currently have a non-webhook integration for Codebase. But Codebase also has a dedicated webhook API called Event Hooks. We should see if we can quickly write a webhook implementation for it at some point.

I might take this up eventually if no one else does! Thanks! :)

@timabbott: FYI :)

@zulipbot
Copy link
Member

Hello @zulip/server-integrations members, this issue was labeled with the "area: integrations" label, so you may want to check it out!

@atkm
Copy link
Collaborator

atkm commented Sep 15, 2018

@zulipbot claim

@zulipbot
Copy link
Member

Welcome to Zulip, @atkm! We just sent you an invite to collaborate on this repository at https://github.com/zulip/zulip/invitations. Please accept this invite in order to claim this issue and begin a fun, rewarding experience contributing to Zulip!

Here's some tips to get you off to a good start:

As you work on this issue, you'll also want to refer to the Zulip code contribution guide, as well as the rest of the developer documentation on that site.

See you on the other side (that is, the pull request side)!

@atkm
Copy link
Collaborator

atkm commented Sep 15, 2018

@eeshangarg Is this integration already implemented? There is already a page for Codebase.

@eeshangarg
Copy link
Member Author

eeshangarg commented Sep 17, 2018

@atkm: We have an integration for it, but not a webhook one that uses their dedicated API! If you'd like to take this up, feel free to! Thanks! :)

@atkm
Copy link
Collaborator

atkm commented Sep 18, 2018

@eeshangarg Cool! I'll take a stab at it then.

@zulipbot
Copy link
Member

zulipbot commented Sep 28, 2018

Hello @atkm, you have been unassigned from this issue because you have not updated this issue or any referenced pull requests for over 14 days.

You can reclaim this issue or claim any other issue by commenting @zulipbot claim on that issue.

Thanks for your contributions, and hope to see you again soon!

@dipu989
Copy link
Collaborator

dipu989 commented Oct 20, 2018

@zulipbot claim

@zulipbot
Copy link
Member

zulipbot commented Oct 30, 2018

Hello @dipu989, you have been unassigned from this issue because you have not updated this issue or any referenced pull requests for over 14 days.

You can reclaim this issue or claim any other issue by commenting @zulipbot claim on that issue.

Thanks for your contributions, and hope to see you again soon!

@thedeveloperr
Copy link
Collaborator

@zulipbot claim

@zulipbot
Copy link
Member

zulipbot commented Mar 15, 2019

Hello @thedeveloperr, you have been unassigned from this issue because you have not updated this issue or any referenced pull requests for over 14 days.

You can reclaim this issue or claim any other issue by commenting @zulipbot claim on that issue.

Thanks for your contributions, and hope to see you again soon!

@thedeveloperr
Copy link
Collaborator

@zulipbot still working.

@thedeveloperr
Copy link
Collaborator

@zulipbot claim

@zulipbot
Copy link
Member

zulipbot commented Mar 30, 2019

Hello @thedeveloperr, you have been unassigned from this issue because you have not updated this issue or any referenced pull requests for over 14 days.

You can reclaim this issue or claim any other issue by commenting @zulipbot claim on that issue.

Thanks for your contributions, and hope to see you again soon!

@thedeveloperr
Copy link
Collaborator

@zulipbot claim

@zulipbot
Copy link
Member

zulipbot commented Apr 16, 2019

Hello @thedeveloperr, you have been unassigned from this issue because you have not updated this issue or any referenced pull requests for over 14 days.

You can reclaim this issue or claim any other issue by commenting @zulipbot claim on that issue.

Thanks for your contributions, and hope to see you again soon!

@sameerchoubey
Copy link
Collaborator

@zulipbot claim

@zulipbot
Copy link
Member

zulipbot commented Apr 30, 2019

Hello @sameerchoubey, you have been unassigned from this issue because you have not updated this issue or any referenced pull requests for over 14 days.

You can reclaim this issue or claim any other issue by commenting @zulipbot claim on that issue.

Thanks for your contributions, and hope to see you again soon!

@sameerchoubey
Copy link
Collaborator

@zulipbot I'm still working on this. I would probably open the PR soon.

andersk added a commit to andersk/zulip that referenced this issue Sep 9, 2019
…ons."

This reverts commit 073ecaa (zulip#9395).

This exception handler was overly broad in catching all `OSError`s,
and it made debugging harder by hiding the actual exception.
Furthermore, we no longer use NFS (zulip#12963), and we’re now getting
reports of Windows users running into this message.

Signed-off-by: Anders Kaseorg <anders@zulipchat.com>
andersk added a commit to andersk/zulip that referenced this issue Sep 9, 2019
…ons."

This reverts commit 073ecaa (zulip#9395).

This exception handler was overly broad in catching all `OSError`s,
and it made debugging harder by hiding the actual exception.
Furthermore, we no longer use NFS (zulip#12963), and we’re now getting
reports of Windows users running into this message.

Signed-off-by: Anders Kaseorg <anders@zulipchat.com>
@zulipbot
Copy link
Member

Hello @zulip/server-integrations, @zulip/server-refactoring members, this issue was labeled with the "area: integrations", "area: refactoring" labels, so you may want to check it out!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

8 participants