getsentry / getsentry/sentry

Review OrganizationIncident endpoints to publish or make private

Open
#65,748 0 comments 0 reactions 0 assignees View on GitHub
API Platform Component: API Task
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
1d 5h
Merged PRs (30d)
624

Description

API endpoints to review:

- [ ] `OrganizationIncidentActivityIndexEndpoint::GET`
- [ ] `OrganizationIncidentCommentDetailsEndpoint::DELETE`
- [ ] `OrganizationIncidentCommentDetailsEndpoint::PUT`
- [ ] `OrganizationIncidentCommentIndexEndpoint::POST`
- [ ] `OrganizationIncidentDetailsEndpoint::GET`
- [ ] `OrganizationIncidentDetailsEndpoint::PUT`
- [ ] `OrganizationIncidentIndexEndpoint::GET`
- [ ] `OrganizationIncidentSeenEndpoint::POST`

Documentation on determining if API should or shouldn't be public and how to publish: https://develop.sentry.dev/api/public/

If an endpoint is determined as a candidate to be published, create an issue and link it in this [placeholder epic](https://github.com/getsentry/sentry/issues/61479)

Note: scope of **this ticket** is only to either create ticket for publishing, or marking private/experimental.

If endpoint is determined to be kept private or experimental, it should be marked as such with ApiPublishStatus. Example:

https://github.com/getsentry/sentry/blob/dc65f986f481a27b3a13db224b4a096f009e1a48/src/sentry/api/endpoints/user_notification_email.py#L19-L24

This a minimal change, so no point in creating a separate ticket.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.