Quite often, and decently fast I have to say, when someone reports bug or issue somebody from team tells this PR fixes it. And right after that anxious user makes rebuild or update, returns and cries for help because that fix didn’t change anything. Same poor team member replies that PR isn’t merg…

I’m afraid the answer is: “it depends”. At a minimum, we need to wait for the automated checks to run (about 20 mins), and we need at least one other person on the Team to review/approve the PR. That can take anywhere from minutes to days, depending on availability/priority. If it’s a more complex …

Of course that badge :man_facepalming: Yeah — it depends is a good answer. And expected one too.

PR이 병합되는 시기는 언제인가요?

개발

Jagster (Jakke Flemming) 7월 8, 2022, 8:42오전 3

물론 그 배지

네 — 상황에 따라 다릅니다가 좋은 답변입니다. 그리고 기대되는 답변이기도 하죠.

글		댓글	조회수
Questions about GitHub bug fix commits and tests-passed Development	4	1252	12월 20, 2016
What's the process to get a theme-component PR reviewed? Development easy-responsive-footer	5	511	2월 29, 2024
What is the turn around time for pull request? Development rest-api	2	307	8월 24, 2023
Recommended approach for production discourse using PR (not merged) Support	15	371	2월 21, 2025
Cannot merge users - process never finishes Support	1	120	12월 10, 2024

PR이 병합되는 시기는 언제인가요?

Related topics