Skip to content

Pull requests: openshift/must-gather-operator

New pull request New
21 Open 334 Closed
21 Open 334 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Reviews
Filter by reviews
No reviews Review required Approved review Changes requested
Assignee
Filter by who’s assigned
Assigned to nobody Loading
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Pull requests list

NO-JIRA: Bump golang.org/x deps to fix reachable CVEs jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
#373 opened Jul 8, 2026 by rh-roman Loading…
5
MG-183: Add namespace restrictions for must-gather jobs do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
#371 opened Jul 7, 2026 by neha037 Contributor • Draft
14
OAPE-824: add the agentic docs in must-gather-operator repo jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
#370 opened Jul 6, 2026 by praveencodes Contributor Loading…
20
NOJIRA: Dummy PR automatic addressing code review
#369 opened Jul 2, 2026 by neha037 Contributor Loading…
9
No-Jira | Dummy PR for testing
#367 opened Jun 23, 2026 by neha037 Contributor Loading…
27
NOJIRA : Add CI-Monitor (WIP)
#366 opened Jun 18, 2026 by neha037 Contributor Loading…
8
Add adapter to create Lightspeed Proposal after must-gather completion do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress.
#365 opened Jun 18, 2026 by sakshiep1 • Draft
6 tasks
6
MG-271: Implement standard must-gather directory naming convention jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges.
#364 opened Jun 17, 2026 by neha037 Contributor Loading…
27
MG-265: Make serviceAccountName required for MustGather CR jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges.
#363 opened Jun 16, 2026 by neha037 Contributor Loading…
10 tasks done
@shivprakashmuley
21
chore: remove devppratik from owners approved Indicates a PR has been approved by an approver from all required OWNERS files.
#362 opened Jun 12, 2026 by devppratik Loading…
5
[release-4.22] MG-200: generate the token for each e2e test run approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged.
#361 opened Jun 11, 2026 by openshift-cherrypick-robot Loading…
@praveencodes @shivprakashmuley
7
Boilerplate: Update to 8fb7c801f68dc7e06e8d2ae138c2a98f0b234b56 approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged.
#359 opened Jun 9, 2026 by iamkirkbater Loading…
@swghosh
10
OCPBUGS-87528: Updating ose-support-log-gather-operator-container image to be consistent with ART for 5.0 approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria
#356 opened Jun 8, 2026 by openshift-bot Loading…
@AlexVulaj
8
OAPE-698: Integration of codecov on the must-gather-operator jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
#350 opened May 19, 2026 by praveencodes Contributor Loading…
11
OCPBUGS-79069 - fix the since and sinceTime validation issue
#345 opened Apr 30, 2026 by praveencodes Contributor Loading…
10
MG-230: Migrate to UBI10 base images for RHCOS10/RHEL10 compatibility jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
#338 opened Apr 2, 2026 by KeenonLee Contributor Loading…
19
[WIP] MG-244: OTE migration for Support Log Gather do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
#337 opened Mar 27, 2026 by KeenonLee Contributor Loading…
18
Improve API from kube-api-linter suggestions approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.
#329 opened Mar 12, 2026 by swghosh Member • Draft
13
MG-61: minimal possible get/list RBAC for ServiceAccount running the Job approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
#264 opened Aug 25, 2025 by swghosh Member • Draft
37
fix make generate with tools approved Indicates a PR has been approved by an approver from all required OWNERS files. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.
#263 opened Aug 25, 2025 by swghosh Member Loading…
11
MG-3: Build a guide for local operator development approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.
#246 opened Jul 16, 2025 by swghosh Member • Draft
12
ProTip! no:milestone will show everything without a milestone.