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.

Sign up for GitHub

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

Jump to bottom

RFE: Add more event types to get parity with GitHub event types #2113

Closed
6 of 13 tasks
stephenc opened this issue Jul 4, 2017 · 7 comments
Closed
6 of 13 tasks

RFE: Add more event types to get parity with GitHub event types #2113

stephenc opened this issue Jul 4, 2017 · 7 comments
Labels
issue/stale type/enhancement An improvement of existing functionality type/feature Completely new functionality. Can only be merged if feature freeze is not active.

Comments

@stephenc
Copy link

stephenc commented Jul 4, 2017 •
edited by lunny
Loading

  • Gitea version (or commit ref): N/A
  • Git version: N/A
  • Operating system: N/A
  • Database (use [x]): N/A
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io: N/A
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:

Description

Please add more event types to bring closer parity to the GitHub event types:

screen shot 2017-07-04 at 22 13 51

Specifically, first round targets:

  • Repository
  • Pull request review comment
  • Delete
  • Fork
  • Issues
  • Issue comment

The others are not really relevant for the current feature set
@stephenc stephenc mentioned this issue Jul 4, 2017
Closed
7 tasks
@lunny lunny added the type/feature Completely new functionality. Can only be merged if feature freeze is not active. label Jul 5, 2017
@lunny lunny added this to the 1.x.x milestone Jul 5, 2017
@bkcsoft bkcsoft added the type/enhancement An improvement of existing functionality label Jul 5, 2017
@ethantkoenig
Copy link
Member

See #1663, which adds support for "repository" events

@ethantkoenig ethantkoenig mentioned this issue Aug 25, 2017
Merged
@lunny lunny mentioned this issue Sep 14, 2017
Closed
6 tasks
@lunny
Copy link
Member

lunny commented Sep 14, 2017

maybe a duplicated with #2418

@lunny
Copy link
Member

lunny commented May 17, 2018

Only Pull request review comment left here since #3929 merged.

@lunny lunny mentioned this issue May 21, 2018
Open
7 tasks
@stale
Copy link

stale bot commented Jan 26, 2019

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.

@stale stale bot added the issue/stale label Jan 26, 2019
@stephenc
Copy link
Author

@lunny any eta on Pull request review comment ?

@lunny
Copy link
Member

lunny commented Feb 6, 2019

@stephenc I think that has been resolved. Sorry to forget close this issue, see #5027.

@lunny lunny closed this as completed Feb 6, 2019
@lunny lunny removed this from the 1.x.x milestone Feb 6, 2019
@lunny
Copy link
Member

lunny commented Feb 6, 2019

All event types have been implemented on v1.7.x

@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
issue/stale type/enhancement An improvement of existing functionality type/feature Completely new functionality. Can only be merged if feature freeze is not active.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@lunny @stephenc @bkcsoft @ethantkoenig