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

chore(docs): Add statusDetails info to endpoint doc #82017

Merged
merged 3 commits into from
Dec 12, 2024
Merged

chore(docs): Add statusDetails info to endpoint doc #82017

merged 3 commits into from
Dec 12, 2024

Conversation

jangjodi
Copy link
Member

Add more details about statusDetails to Update an Issue endpoint doc
Doc now matches the info for the bulk endpoint: https://docs.sentry.io/api/events/bulk-mutate-a-list-of-issues/

fixes #66402

@jangjodi jangjodi requested review from a team as code owners December 12, 2024 18:14
@github-actions github-actions bot added Scope: Frontend Automatically applied to PRs that change frontend components Scope: Backend Automatically applied to PRs that change backend components labels Dec 12, 2024
@github-actions GitHub Actions
Copy link
Contributor

🚨 Warning: This pull request contains Frontend and Backend changes!

It's discouraged to make changes to Sentry's Frontend and Backend in a single pull request. The Frontend and Backend are not atomically deployed. If the changes are interdependent of each other, they must be separated into two pull requests and be made forward or backwards compatible, such that the Backend or Frontend can be safely deployed independently.

Have questions? Please ask in the #discuss-dev-infra channel.

@jangjodi
Copy link
Member Author

🚨 Warning: This pull request contains Frontend and Backend changes!

It's discouraged to make changes to Sentry's Frontend and Backend in a single pull request. The Frontend and Backend are not atomically deployed. If the changes are interdependent of each other, they must be separated into two pull requests and be made forward or backwards compatible, such that the Backend or Frontend can be safely deployed independently.

Have questions? Please ask in the #discuss-dev-infra channel.

fyi I just removed the BE change. Not sure if automation will pick up on that

@jangjodi jangjodi mentioned this pull request Dec 12, 2024
Merged
@jangjodi @snigdhas
ref: Reword
97caea2 
Co-authored-by: Snigdha Sharma <[email protected]>
@jangjodi jangjodi added Scope: Frontend Automatically applied to PRs that change frontend components and removed Scope: Frontend Automatically applied to PRs that change frontend components Scope: Backend Automatically applied to PRs that change backend components labels Dec 12, 2024
@jangjodi jangjodi merged commit 0a40b01 into master Dec 12, 2024
36 of 37 checks passed
@jangjodi jangjodi deleted the jodi/issue-details-endpoint-doc branch December 12, 2024 19:45
evanh pushed a commit that referenced this pull request Dec 17, 2024
@jangjodi @snigdhas @evanh
chore(docs): Add statusDetails info to endpoint doc (#82017)
a13537c 
Add more details about statusDetails to Update an Issue endpoint doc

Co-authored-by: Snigdha Sharma <[email protected]>
@github-actions github-actions bot locked and limited conversation to collaborators Dec 28, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Reviewers

@snigdhas snigdhas snigdhas approved these changes

Assignees
No one assigned
Labels
Scope: Frontend Automatically applied to PRs that change frontend components
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Align docs for resolving an issue (missing statusDetails param)
2 participants
@jangjodi @snigdhas