[Payment due @huult] [No QA] Let workspace admins delete tasks in workspace rooms by lakchote · Pull Request #102661 · Expensify/App

lakchote · 2026-09-30T13:50:56Z

Explanation of Change

Workspace admins couldn't delete a task that someone else created in one of their workspace rooms. The task details page only showed Delete to the task creator, so an admin had no way to remove spam tasks posted by other people in a public room.

Now the task details page also shows Delete to an admin of the task's workspace, as long as the workspace isn't a personal one and the parent room isn't archived. It uses the same Delete button and confirmation as for the creator.

Fixed Issues

$ https://github.com/Expensify/Expensify/issues/681309
PROPOSAL:

Tests

Prerequisite: Account A is a new account whose email has no +. During onboarding it picked "Manage my team's expenses", which creates a workspace with setup tasks in its #admins room.

As account A, press + > Start chat > Room, pick the workspace from onboarding, set Visibility to Public and create the room.
As account B, who isn't a workspace member, open the room's URL. Then press + > Assign task in the composer and create two tasks, leaving Assignee empty.
As B, mark the second task as complete.
As B, open the first task's details and verify Delete is shown.
As A, switch the workspace to Control under Overview > Plan type if it isn't already. Then go to Members > Invite member and invite account C as a Member and account D as an Auditor.
As C and then as D, open the first task's details and verify Delete isn't shown.
As A, open the second task's details and verify Delete isn't shown while it's completed.
As A, press Mark as incomplete on the second task, then verify Delete is shown.
As A, open the first task's details, press Delete and confirm. Verify the task is removed from the room.
As B, create a task in a DM with A and assign it to A.
As A, open that task's details and verify Delete isn't shown.
As A, open one of the setup tasks in #admins, for example "Invite your team", and verify Delete isn't shown.

Screen.Recording.2026-09-30.at.18.54.12.mov

Verify that no errors appear in the JS console

Offline tests

As A, open the details of one of B's incomplete tasks in the public room while online.
Go offline, press Delete and confirm.
Verify the task is shown as deleted.
Go back online and verify the delete goes through.

QA Steps

Same as tests.

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

codecov · 2026-09-30T13:54:40Z

Codecov Report

✅ Changes either increased or maintained existing code coverage, great job!

Files with missing lines	Coverage Δ
src/libs/actions/Task.ts	`67.04% <100.00%> (+0.97%)`	⬆️
...eportDetailsPage/ReportDetailsTaskDeleteAction.tsx	`100.00% <100.00%> (ø)`
... and 297 files with indirect coverage changes

melvin-bot · 2026-09-30T17:05:56Z

@hoangzinh Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

chatgpt-codex-connector · 2026-09-30T17:06:03Z

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-09-30T17:20:53.752931Z	`1e77e6c`	Draft marked ready

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

trjExpensify

Makes sense 👍

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 1e77e6c609

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

hoangzinh · 2026-10-01T08:42:20Z

Reviewer Checklist

I have verified the author checklist is complete (all boxes are checked off).
I verified the correct issue is linked in the ### Fixed Issues section above
I verified testing steps are clear and they cover the changes made in this PR
- I verified the steps for local testing are in the Tests section
- I verified the steps for Staging and/or Production testing are in the QA steps section
- I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
- I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
I checked that screenshots or videos are included for tests on all platforms
I included screenshots or videos for tests on all platforms
I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
I verified tests pass on all platforms & I tested again on:
- Android: HybridApp
- Android: mWeb Chrome
- iOS: HybridApp
- iOS: mWeb Safari
- MacOS: Chrome / Safari
If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
I verified proper code patterns were followed (see Reviewing the code)
- I verified that comments were added to code that is not self explanatory
- I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
- I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
I verified that this PR follows the guidelines as stated in the Review Guidelines
I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
If a new component is created I verified that:
- A similar component doesn't exist in the codebase
- All props are defined accurately
- The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
- The only data being stored in the state is data necessary for rendering and nothing else
- The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
If a new CSS style is added I verified that:
- A similar style doesn't already exist
- The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)
If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
- I verified that all the inputs inside a form are aligned with each other.
- I added Design label and/or tagged @Expensify/design so the design team can review the changes.
If the PR adds or modifies the UI:
- I asked an AI agent to review the changes for accessibility issues and addressed its findings.
- I tested with a screen reader (VoiceOver on macOS) and verified all new/changed elements are reachable with a logical focus order.
- I verified all new/changed elements have meaningful accessible names and roles.
- I verified state changes are announced (e.g. checked/unchecked, expanded/collapsed, selected).
For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this flow.
If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: HybridApp

Android: mWeb Chrome

iOS: HybridApp

iOS: mWeb Safari

MacOS: Chrome / Safari

hoangzinh · 2026-10-01T11:21:05Z


+    // Setup tasks are completed automatically by later setup flows, which fails once the task is deleted
+    const isTaskOwnedByGuideOrConcierge = report.ownerAccountID === CONST.ACCOUNT_ID.CONCIERGE || (!!report.ownerAccountID && !!guideAccountIDs?.includes(report.ownerAccountID));
+    const canDeleteTaskAsPolicyAdmin = isPolicyAdmin && policy?.type !== CONST.POLICY.TYPE.PERSONAL && !isParentReportArchived && !isTaskOwnedByGuideOrConcierge;


@lakchote will we only allow admins to be able to delete a task in workspace rooms? Or all other chat reports? (i.e employees' workspace chats, expense reports...)

Only tasks in workspace rooms @hoangzinh

lakchote · 2026-10-05T10:08:18Z

@hoangzinh can you finish your review please?

lakchote · 2026-10-07T14:21:16Z

Reassigning to @huult, @hoangzinh got sick

huult · 2026-10-07T14:23:31Z

Reviewer Checklist

I have verified the author checklist is complete (all boxes are checked off).
I verified the correct issue is linked in the ### Fixed Issues section above
I verified testing steps are clear and they cover the changes made in this PR
- I verified the steps for local testing are in the Tests section
- I verified the steps for Staging and/or Production testing are in the QA steps section
- I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
- I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
I checked that screenshots or videos are included for tests on all platforms
I included screenshots or videos for tests on all platforms
I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
I verified tests pass on all platforms & I tested again on:
- Android: HybridApp
- Android: mWeb Chrome
- iOS: HybridApp
- iOS: mWeb Safari
- MacOS: Chrome / Safari
If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
I verified proper code patterns were followed (see Reviewing the code)
- I verified that comments were added to code that is not self explanatory
- I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
- I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
I verified that this PR follows the guidelines as stated in the Review Guidelines
I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
If a new component is created I verified that:
- A similar component doesn't exist in the codebase
- All props are defined accurately
- The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
- The only data being stored in the state is data necessary for rendering and nothing else
- The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
If a new CSS style is added I verified that:
- A similar style doesn't already exist
- The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)
If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
- I verified that all the inputs inside a form are aligned with each other.
- I added Design label and/or tagged @Expensify/design so the design team can review the changes.
If the PR adds or modifies the UI:
- I asked an AI agent to review the changes for accessibility issues and addressed its findings.
- I tested with a screen reader (VoiceOver on macOS) and verified all new/changed elements are reachable with a logical focus order.
- I verified all new/changed elements have meaningful accessible names and roles.
- I verified state changes are announced (e.g. checked/unchecked, expanded/collapsed, selected).
For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this flow.
If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: HybridApp

Screen.Recording.2026-10-08.at.08.57.39.mov

Android: mWeb Chrome

Screen.Recording.2026-10-08.at.08.54.20.mov

iOS: HybridApp

Screen.Recording.2026-10-08.at.09.04.18.mov

iOS: mWeb Safari

Screen.Recording.2026-10-08.at.09.05.32.mov

MacOS: Chrome / Safari

Screen.Recording.2026-10-08.at.08.48.27.mov

huult · 2026-10-07T15:17:36Z

Unrelated changes

Five files in this PR have nothing to do with the task Delete change. They are whitespace-only (trailing spaces removed), and they came in through the "merge main" commits:

docs/articles/new-expensify/ai-agents/Use-Agent-Templates.md
docs/articles/travel/company-setup/Enable-Travel-on-a-Workspace.md
docs/articles/travel/travel-policy/Configuring-Hotel-Settings.md
patches/pusher-js/details.md
patches/@shopify/react-native-skia/@shopify+react-native-skia+2.11.2+005+load-skia-web-fail-closed.patch

git diff -w --ignore-space-at-eol origin/main...HEAD shows no difference for any of them.

Please revert these. The .patch file is the riskiest one: a blank context line in a hunk changed from " " to "", and we apply patches with patch-package, so I would not touch it. The docs changes also add reviewers for no reason.

git checkout origin/main -- <the five files above>

huult · 2026-10-07T15:28:33Z

+    const isTaskOwnedByGuideOrConcierge = report?.ownerAccountID === CONST.ACCOUNT_ID.CONCIERGE || (!!report?.ownerAccountID && !!guideAccountIDs?.includes(report.ownerAccountID));
+
+    // Setup flows later complete these tasks, including when another admin has no matching personal onboarding data
+    const isSetupTask = isAdminRoom(parentReport) && isTaskOwnedByGuideOrConcierge;
+    const canDeleteTaskAsPolicyAdmin =
+        isPolicyAdmin(policy) &&
+        policy?.type !== CONST.POLICY.TYPE.PERSONAL &&
+        (isUserCreatedPolicyRoom(parentReport) || isDefaultRoom(parentReport)) &&
+        !isParentReportArchived &&
+        !isSetupTask;


@lakchote I think we should move this logic into src/libs/actions/Task.ts by adding a canDeleteTaskAsPolicyAdmin function there. Then the component would only need one line to call it. This would make the code easier to read and easier to unit test.

Good call, moved it to canDeleteTaskAsPolicyAdmin in Task.ts next to canModifyTask and added a test.

huult · 2026-10-07T15:31:03Z


+    const isTaskOwnedByGuideOrConcierge = report?.ownerAccountID === CONST.ACCOUNT_ID.CONCIERGE || (!!report?.ownerAccountID && !!guideAccountIDs?.includes(report.ownerAccountID));
+
+    // Setup flows later complete these tasks, including when another admin has no matching personal onboarding data


Suggested change

// Setup flows later complete these tasks, including when another admin has no matching personal onboarding data

// Guide/Concierge setup tasks in #admins are completed by the onboarding flow, so admins should not delete them

@lakchote can we update like this?

lakchote · 2026-10-07T18:32:07Z

Good catch, reverted those 5 files.

huult

LGTM.

The code changes are working as described.

melvin-bot · 2026-10-08T02:16:31Z

@MariaHCD Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

melvin-bot · 2026-10-08T02:16:33Z

🎯 @huult, thanks for reviewing and testing this PR! 🎉

A payment issue will be created for your review once this PR is deployed to production.
E/E issue linked to the PR - https://www.github.com/Expensify/Expensify/issues/681309.

If payment is not needed (e.g., regression PR review fix etc), react with 👎 to this comment to prevent the payment issue from being created.

OSBotify · 2026-10-08T14:36:31Z

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

github-actions · 2026-10-08T14:36:34Z

🚧 MariaHCD has triggered a test Expensify/App build. You can view the workflow run here.

github-actions · 2026-10-08T14:42:34Z

🧪🧪 Use the links below to test this adhoc build on Android, iOS, and Web. Happy testing! 🧪🧪
Built from App PR #102661.

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-ba51cdc-b8010af-63fae9e5619642ac74506825a462da306ad58ec4/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-ba51cdc-b8010af-e6ab656984e1fbacb21d083703336c1491d7dfcd/index.html

Web 🕸️
https://102661.pr-testing.expensify.com

👀 View the workflow run that generated this build 👀

OSBotify · 2026-10-08T19:44:58Z

🚀 Deployed to staging by https://github.com/MariaHCD in version: 9.5.6-0 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

MelvinBot · 2026-10-08T19:51:49Z

No help site update is needed. No article says who can delete a task, so letting workspace admins delete other people's tasks in workspace rooms doesn't make any existing sentence wrong. The closest article, Assign a Task via Chat, only lists editing actions for the creator and assignee, and those are unchanged.

view run

OSBotify · 2026-10-09T20:30:35Z

🚀 Deployed to production by https://github.com/puneetlath in version: 9.5.6-6 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

Bundle Size Analysis (Sentry):

Android
iOS

lakchote added 2 commits September 30, 2026 15:24

show task Delete to workspace admins

68ef9fa

add tests for admin task Delete

1e77e6c

melvin-bot Bot assigned lakchote Sep 30, 2026

lakchote marked this pull request as ready for review September 30, 2026 17:05

lakchote requested review from a team as code owners September 30, 2026 17:05

melvin-bot Bot requested review from hoangzinh and trjExpensify and removed request for a team September 30, 2026 17:05

melvin-bot Bot removed the request for review from a team September 30, 2026 17:05

trjExpensify previously approved these changes Sep 30, 2026

View reviewed changes

chatgpt-codex-connector Bot reviewed Sep 30, 2026

View reviewed changes

Comment thread src/pages/DynamicReportDetailsPage/index.tsx Outdated

hoangzinh reviewed Oct 1, 2026

View reviewed changes

merge main into lucien/admin-delete-tasks-workspace-rooms

2eca4b1

lakchote dismissed trjExpensify’s stale review via 2eca4b1 October 2, 2026 05:50

lakchote requested a review from stephanieelliott as a code owner October 2, 2026 05:50

github-actions Bot changed the title ~~Let workspace admins delete tasks in workspace rooms~~ [No QA] Let workspace admins delete tasks in workspace rooms Oct 2, 2026

This comment has been minimized.

Sign in to view

lakchote added 2 commits October 2, 2026 15:45

fix setup task deletion exception

793b7e4

add task deletion permission regression tests

be5b329

This comment has been minimized.

Sign in to view

merge main into admin task deletion

45d3120

This comment has been minimized.

Sign in to view

merge main into lucien/admin-delete-tasks-workspace-rooms

17f2070

lakchote requested a review from huult October 7, 2026 14:20

huult reviewed Oct 7, 2026

View reviewed changes

lakchote added 8 commits October 7, 2026 18:54

revert whitespace-only change in agent templates doc

bfbce9d

revert whitespace-only change in travel setup doc

96da73d

revert whitespace-only change in hotel settings doc

78d9b61

revert whitespace-only change in pusher-js patch notes

06beabb

revert whitespace-only change in skia web patch

de209cc

add canDeleteTaskAsPolicyAdmin to task actions

46ddbcb

use canDeleteTaskAsPolicyAdmin in task delete action

a0bcf58

add canDeleteTaskAsPolicyAdmin tests

df32e1a

huult approved these changes Oct 8, 2026

View reviewed changes

melvin-bot Bot requested a review from MariaHCD October 8, 2026 02:16

melvin-bot Bot changed the title ~~[No QA] Let workspace admins delete tasks in workspace rooms~~ [Payment due @huult] [No QA] Let workspace admins delete tasks in workspace rooms Oct 8, 2026

MariaHCD approved these changes Oct 8, 2026

View reviewed changes

MariaHCD merged commit ba51cdc into main Oct 8, 2026
44 of 49 checks passed

MariaHCD deleted the lucien/admin-delete-tasks-workspace-rooms branch October 8, 2026 14:31

OSBotify mentioned this pull request Oct 8, 2026

Deploy Checklist: New Expensify 2026-10-08 #103502

Closed

90 tasks done


		const isTaskOwnedByGuideOrConcierge = report?.ownerAccountID === CONST.ACCOUNT_ID.CONCIERGE \|\| (!!report?.ownerAccountID && !!guideAccountIDs?.includes(report.ownerAccountID));

		// Setup flows later complete these tasks, including when another admin has no matching personal onboarding data

	// Setup flows later complete these tasks, including when another admin has no matching personal onboarding data
	// Guide/Concierge setup tasks in #admins are completed by the onboarding flow, so admins should not delete them

Conversation

lakchote commented Sep 30, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Explanation of Change

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

Uh oh!

codecov Bot commented Sep 30, 2026 • edited by github-actions Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

melvin-bot Bot commented Sep 30, 2026

Uh oh!

chatgpt-codex-connector Bot commented Sep 30, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codex Review Summary

Uh oh!

trjExpensify left a comment

Choose a reason for hiding this comment

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

hoangzinh commented Oct 1, 2026

Reviewer Checklist

Screenshots/Videos

Uh oh!

hoangzinh Oct 1, 2026

Choose a reason for hiding this comment

Uh oh!

lakchote Oct 2, 2026

Choose a reason for hiding this comment

Uh oh!

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

lakchote commented Oct 5, 2026

Uh oh!

lakchote commented Oct 7, 2026

Uh oh!

huult commented Oct 7, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Reviewer Checklist

Screenshots/Videos

Uh oh!

huult commented Oct 7, 2026

Uh oh!

huult Oct 7, 2026

Choose a reason for hiding this comment

Uh oh!

lakchote Oct 7, 2026

Choose a reason for hiding this comment

Uh oh!

huult Oct 7, 2026

Choose a reason for hiding this comment

Uh oh!

lakchote Oct 7, 2026

Choose a reason for hiding this comment

Uh oh!

lakchote commented Oct 7, 2026

Uh oh!

huult left a comment

Choose a reason for hiding this comment

Uh oh!

melvin-bot Bot commented Oct 8, 2026

Uh oh!

melvin-bot Bot commented Oct 8, 2026

Uh oh!

Uh oh!

OSBotify commented Oct 8, 2026

Uh oh!

github-actions Bot commented Oct 8, 2026

Uh oh!

lakchote commented Sep 30, 2026 •

edited

Loading

codecov Bot commented Sep 30, 2026 •

edited by github-actions Bot

Loading

chatgpt-codex-connector Bot commented Sep 30, 2026 •

edited

Loading

huult commented Oct 7, 2026 •

edited

Loading