Project

General

Profile

Actions

Bug #19551

closed

Backport commits for CI failures

Added by hsbt (Hiroshi SHIBATA) over 1 year ago. Updated over 1 year ago.

Status:
Closed
Assignee:
-
Target version:
-
[ruby-core:113028]

Description

I created PRs to fix CI failure for stable or old stable branches.

Please merge them before release time.


Can I merge PR like "Fix CI failure" for stable branches myself from April 2023?

I can maintain to keep CI status with my full-time job. It helps to release work for all of branch maintainers.

Actions #1

Updated by hsbt (Hiroshi SHIBATA) over 1 year ago

  • Description updated (diff)
Actions #2

Updated by hsbt (Hiroshi SHIBATA) over 1 year ago

  • Backport changed from 2.7: REQUIRED, 3.0: REQUIRED, 3.1: DONTNEED, 3.2: REQUIRED to 2.7: REQUIRED, 3.0: REQUIRED, 3.1: DONTNEED, 3.2: DONE
Actions #3

Updated by hsbt (Hiroshi SHIBATA) over 1 year ago

  • Backport changed from 2.7: REQUIRED, 3.0: REQUIRED, 3.1: DONTNEED, 3.2: DONE to 2.7: DONE, 3.0: DONE, 3.1: DONTNEED, 3.2: DONE

Updated by nagachika (Tomoyuki Chikanaga) over 1 year ago

Thank you very much as always for your hard work.
As for your question, I believe there is no problem with merging pull requests that involve obvious fixes, such as fixing CI failures, into stable branches.

Updated by hsbt (Hiroshi SHIBATA) over 1 year ago

I asked @usa (Usaku NAKAMURA) and @naruse (Yui NARUSE). old stable branch like ruby_3_1 and security maintenance branch like ruby_3_0 remain the current workflow that is I submit a pull-request or patch, usa will merge it.

I try to fix CI failure only stable branch like ruby_3_2 at first. Thank you.

Actions

Also available in: Atom PDF

Like0
Like0Like0Like0Like0Like0