# 토픽 첫 게시글 수정 시 REST API 호출에서 bypass\_bump에 대한 감사

**URL:** <https://meta.discourse.org/t/appreciation-for-bypass-bump-in-rest-api-calls-to-edit-first-post-in-topics/381366>\
**Category:** Development\
**Created:** [9월 2, 2025, 8:56오후 UTC](https://meta.discourse.org/t/appreciation-for-bypass-bump-in-rest-api-calls-to-edit-first-post-in-topics/381366 "2025-09-02T20:56:34Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![Ethsim2](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ethsim2/32/522255_2.png) [@Ethsim2](https://meta.discourse.org/u/Ethsim2)\
**Post date:** [10월 2, 2025, 6:03오후 UTC](https://meta.discourse.org/t/appreciation-for-bypass-bump-in-rest-api-calls-to-edit-first-post-in-topics/381366/7 "2025-10-02T18:03:21Z")

</div>

음, 이 주제를 다시 읽어보니 대학에 다닐 때 활동하지 않았고 코딩할 시간이 있었을 때 관련 PR을 하나 더 포함시키지 않았다는 걸 깨달았어요.

> <https://github.com/discourse/discourse/pull/34712>
>
> This PR adds an optional \`bypass\_bump\` parameter to the post update API and
> plu…mbs it through to \`PostRevisor\`.
> 
> \*\*Use case\*\*
> Automated integrations (e.g., ICS → Discourse sync) often need to update
> content or tags without bumping the topic. An explicit flag makes this
> deterministic, without relying on heuristics.
> 
> \*\*Behavior\*\*
> \- \`bypass\_bump=true\` can be sent as a top-level param or nested under \`post\[bypass\_bump\]\`.
> \- If omitted, behavior is unchanged.
> \- Only affects whether the topic’s \`bumped\_at\` is updated.
> 
> \*\*Status\*\*
> Opening as a spike for discussion. I’m aware of PR #34681 which changes
> bumping semantics more broadly; this PR demonstrates an explicit alternative
> for API clients.

---

_[View the full topic](https://meta.discourse.org/t/appreciation-for-bypass-bump-in-rest-api-calls-to-edit-first-post-in-topics/381366)._