[POC] Dynamic checklist #27532

sebryu · 2023-09-15T14:18:47Z

Details

We have a PR author and reviewer checklists to help authors and reviewers to follow our best practices, promote high code quality and consistency, and to reduce the likelihood of introducing bugs. We want to automate this process and add some checks only if we detect that it's relevant.

Fixed Issues

$ #24444

PROPOSAL:
Author Checklist action will now add new dynamic checks based on content of the PR. It's more of a skeleton right now, but after merging this we can migrate existing checks from PULL_REQUEST_TEMPLATE into string arrays inside authorChecklist.js and add them only if we detect that they are relevant

Tests

Verify that no errors appear in the JS console

Offline tests

QA Steps

Verify that no errors appear in the JS console

PR Author Checklist

I linked the correct issue in the ### Fixed Issues section above
I wrote clear testing steps that cover the changes made in this PR
- I added steps for local testing in the Tests section
- I added steps for the expected offline behavior in the Offline steps section
- I added steps for Staging and/or Production testing in the QA steps section
- I added steps to cover 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 tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
I included screenshots or videos for tests on all platforms
I ran the tests on all platforms & verified they passed on:
- Android / native
- Android / Chrome
- iOS / native
- iOS / Safari
- MacOS / Chrome / Safari
- MacOS / Desktop
I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
I followed proper code patterns (see Reviewing the code)
- I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
- I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
- 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 shown in the product is localized by adding it to src/languages/* files and using the translation method
  - If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
- I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
- 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 approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
- I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
- I verified the JSDocs style guidelines (in STYLE.md) were followed
If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
I followed the guidelines as stated in the Review Guidelines
I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
I verified that if a function's arguments changed that all usages have also been updated correctly
If a new component is created I verified that:
- A similar component doesn't exist in the codebase
- All props are defined accurately and each prop has a /** comment above it */
- The file is named correctly
- 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
- If we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes
- For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
- Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
- All JSX used for rendering exists in the render method
- 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 any new file was added I verified that:
- The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
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(themeColors.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 a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
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 author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web

Mobile Web - Chrome

Mobile Web - Safari

Desktop

iOS

Android

…elevant anymore

github-actions · 2023-09-15T14:19:02Z

CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅

sebryu · 2023-09-15T20:51:37Z

I have read the CLA Document and I hereby sign the CLA

…t component

…ments

sebryu · 2023-11-03T21:07:13Z

@roryabraham I've applied your suggestions. It took me a while to understand promiseRaceTo but after testing that it looks great 👍 Let me know if you have other suggestions and I will do final testing next week.

.github/actions/javascript/authorChecklist/authorChecklist.ts

roryabraham · 2023-11-03T22:51:33Z

@sebryu looks like we've got some lint errors.

roryabraham

if we detect that dynamicCheck is already added to PR body, but it's unchecked we set isPassing flag to false for slight optimization of not running checkPRForCompletedChecklist

Ok, I see what you mean now. isPassing is a performance optimization. However, I ran some simple benchmarks using the body of this PR to see how long checkPRForCompletedChecklist would take.

Click to expand!

const prBody = `
<!-- If necessary, assign reviewers that know the area or changes well. Feel free to tag any additional reviewers you see fit. -->

### Details
We have a PR author and reviewer checklists to help authors and reviewers to follow our best practices, promote high code quality and consistency, and to reduce the likelihood of introducing bugs. We want to automate this process and add some checks only if we detect that it's relevant.

### Fixed Issues
$ https://github.com/Expensify/App/issues/24444

PROPOSAL: 
Author Checklist action will now add new dynamic checks based on content of the PR. It's more of a skeleton right now, but after merging this we can migrate existing checks from PULL_REQUEST_TEMPLATE into string arrays inside authorChecklist.js and add them only if we detect that they are relevant

### Tests
<!---
Add a numbered list of manual tests you performed that validates your changes work on all platforms, and that there are no regressions present.
Add any additional test steps if test steps are unique to a particular platform.
Manual test steps should be written so that your reviewer can repeat and verify one or more expected outcomes in the development environment.

For example:
1. Click on the text input to bring it into focus
2. Upload an image via copy paste
3. Verify a modal appears displaying a preview of that image
--->

- [x] Verify that no errors appear in the JS console

### Offline tests
<!---
Add any relevant steps that validate your changes work as expected in a variety of network states e.g. "offline", "spotty connection", "slow internet", etc. Manual test steps should be written so that your reviewer and QA testers can repeat and verify one or more expected outcomes. If you are unsure how the behavior should work ask for advice in the \`#expensify-open-source\` Slack channel.
--->

### QA Steps
<!---
Add a numbered list of manual tests that can be performed by our QA engineers on the staging environment to validate that your changes work on all platforms, and that there are no regressions present.
Add any additional QA steps if test steps are unique to a particular platform.
Manual test steps should be written so that the QA engineer can repeat and verify one or more expected outcomes in the staging environment.

For example:
1. Click on the text input to bring it into focus
2. Upload an image via copy paste
3. Verify a modal appears displaying a preview of that image
--->

- [x] Verify that no errors appear in the JS console

### PR Author Checklist
<!--
This is a checklist for PR authors. Please make sure to complete all tasks and check them off once you do, or else your PR will not be merged!
-->

- [x] I linked the correct issue in the \`### Fixed Issues\` section above
- [x] I wrote clear testing steps that cover the changes made in this PR
    - [x] I added steps for local testing in the \`Tests\` section
    - [x] I added steps for the expected offline behavior in the \`Offline steps\` section
    - [x] I added steps for Staging and/or Production testing in the \`QA steps\` section
    - [x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    - [x] 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)
    - [x] I tested this PR with a [High Traffic account](https://github.com/Expensify/App/blob/main/contributingGuides/CONTRIBUTING.md#high-traffic-accounts) against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
- [x] I included screenshots or videos for tests on [all platforms](https://github.com/Expensify/App/blob/main/contributingGuides/CONTRIBUTING.md#make-sure-you-can-test-on-all-platforms)
- [x] I ran the tests on **all platforms** & verified they passed on:
    - [x] Android / native
    - [x] Android / Chrome
    - [x] iOS / native
    - [x] iOS / Safari
    - [x] MacOS / Chrome / Safari
    - [x] MacOS / Desktop
- [x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
- [x] I followed proper code patterns (see [Reviewing the code](https://github.com/Expensify/App/blob/main/contributingGuides/PR_REVIEW_GUIDELINES.md#reviewing-the-code))
    - [x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. \`toggleReport\` and not \`onIconClick\`)
    - [x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. \`myBool && <MyComponent />\`.
    - [x] I verified that comments were added to code that is not self explanatory
    - [x] 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.
    - [x] I verified any copy / text shown in the product is localized by adding it to \`src/languages/*\` files and using the [translation method](https://github.com/Expensify/App/blob/4bd99402cebdf4d7394e0d1f260879ea238197eb/src/components/withLocalize.js#L60)
      - [x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
    - [x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the [localization methods](https://github.com/Expensify/App/blob/4bd99402cebdf4d7394e0d1f260879ea238197eb/src/components/withLocalize.js#L60-L68)
    - [x] 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 approved by marketing by adding the \`Waiting for Copy\` label for a copy review on the original GH to get the correct copy.
    - [x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
    - [x] I verified the JSDocs style guidelines (in [\`STYLE.md\`](https://github.com/Expensify/App/blob/main/contributingGuides/STYLE.md#jsdocs)) were followed
- [x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
- [x] I followed the guidelines as stated in the [Review Guidelines](https://github.com/Expensify/App/blob/main/contributingGuides/PR_REVIEW_GUIDELINES.md)
- [x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like \`Avatar\`, I verified the components using \`Avatar\` are working as expected)
- [x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
- [x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
- [x] I verified that if a function's arguments changed that all usages have also been updated correctly
- [x] If a new component is created I verified that:
    - [x] A similar component doesn't exist in the codebase
    - [x] All props are defined accurately and each prop has a \`/** comment above it */\`
    - [x] The file is named correctly
    - [x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
    - [x] The only data being stored in the state is data necessary for rendering and nothing else
    - [x] If we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes
    - [x] For Class Components, any internal methods passed to components event handlers are bound to \`this\` properly so there are no scoping issues (i.e. for \`onClick={this.submit}\` the method \`this.submit\` should be bound to \`this\` in the constructor)
    - [x] Any internal methods bound to \`this\` are necessary to be bound (i.e. avoid \`this.submit = this.submit.bind(this);\` if \`this.submit\` is never passed to a component event handler like \`onClick\`)
    - [x] All JSX used for rendering exists in the render method
    - [x] 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
- [x] If any new file was added I verified that:
    - [x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
- [x] If a new CSS style is added I verified that:
    - [x] A similar style doesn't already exist
    - [x] The style can't be created with an existing [StyleUtils](https://github.com/Expensify/App/blob/main/src/styles/StyleUtils.js) function (i.e. \`StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)\`)
- [x] 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.
- [x] 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)
- [x] 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.
- [x] 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.
- [x] If a new page is added, I verified it's using the \`ScrollView\` component to make it scrollable when more elements are added to the page.
- [x] 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.
- [x] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.


### Screenshots/Videos
<detailz>
<summary>Web</summary>

<!-- add screenshots or videos here -->

</detailz>

<detailz>
<summary>Mobile Web - Chrome</summary>

<!-- add screenshots or videos here -->

</detailz>

<detailz>
<summary>Mobile Web - Safari</summary>

<!-- add screenshots or videos here -->

</detailz>

<detailz>
<summary>Desktop</summary>

<!-- add screenshots or videos here -->

</detailz>

<detailz>
<summary>iOS</summary>

<!-- add screenshots or videos here -->

</detailz>

<detailz>
<summary>Android</summary>

<!-- add screenshots or videos here -->

</detailz>
`;

function checkPRForCompletedChecklist(expectedNumberOfChecklistItems, checklist) {
    const numberOfFinishedChecklistItems = (checklist.match(/- \[x\]/gi) ?? []).length;
    const numberOfUnfinishedChecklistItems = (checklist.match(/- \[ \]/g) ?? []).length;

    const minCompletedItems = expectedNumberOfChecklistItems - 2;

    console.log(`You completed ${numberOfFinishedChecklistItems} out of ${expectedNumberOfChecklistItems} checklist items with ${numberOfUnfinishedChecklistItems} unfinished items`);

    if (numberOfFinishedChecklistItems >= minCompletedItems && numberOfUnfinishedChecklistItems === 0) {
        console.log('PR Author checklist is complete 🎉');
        return;
    }

    console.log(`Make sure you are using the most up to date checklist found here: ${pathToAuthorChecklist}`);
    console.log("PR Author Checklist is not completely filled out. Please check every box to verify you've thought about the item.");
}

const startTime = new Date();
checkPRForCompletedChecklist(59, prBody.repeat(10000));
const endTime = new Date();

console.log('Time elapsed:', endTime - startTime);

And for this PR it took only 3ms. If we make a super contrived, impossible worst-case-scenario where the PR body is 10000x longer, it takes only about 80ms. So the performance optimization is not worth it. Let's strive instead for simplicity and remove the isPassing optimization and just let checkPRForCompletedChecklist do its thing.

roryabraham

Also, just came to the revelation that a better name than promiseRaceTo is Promise.some – so let's call it that instead and instead of making it take a hard-coded desiredValue, make it take a function that returns a boolean

tests/actions/detectReactComponent.test.ts

roryabraham

@sebryu looks like you need to run npm run gh-actions-build

sebryu · 2023-11-09T10:37:22Z

@roryabraham those failure were false negatives - GH action tried to add second "NOTE: This is a compiled file (...)" annotation.
Now perf-tests produces false negatives - not sure if I should ignore them or rerun pipeline?

roryabraham · 2023-11-10T22:17:57Z

Reassure tests are flaky – this code does not affect the actual app.
snyk is complaining that package.json and package-lock.json are out-of-sync, but it seems to be wrong (with no obvious way to retry the check). Removing node_modules and reinstalling results in no diff in package-lock.json

melvin-bot · 2023-11-10T22:18:11Z

Congrats, that’s your 5th PR merged! 🎉 Do you know about the ContributorPlus role? It’s an opportunity to earn more in the Expensify Open Source community. Keep up the great work - thanks!

melvin-bot · 2023-11-10T22:18:14Z

@roryabraham looks like this was merged without a test passing. Please add a note explaining why this was done and remove the Emergency label if this is not an emergency.

roryabraham · 2023-11-10T22:18:26Z

Not an emergency - see last comment

OSBotify · 2023-11-10T22:27:44Z

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

OSBotify · 2023-11-14T22:11:16Z

🚀 Deployed to staging by https://github.com/roryabraham in version: 1.3.99-0 🚀

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

OSBotify · 2023-11-15T20:54:31Z

🚀 Deployed to production by https://github.com/roryabraham in version: 1.3.99-0 🚀

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

OSBotify · 2023-11-15T21:10:03Z

🚀 Deployed to staging by https://github.com/roryabraham in version: 1.4.0-0 🚀

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

roryabraham and others added 16 commits September 15, 2023 13:33

Add skeleton of dynamicChecklist action

3349d1c

Generate dynamic checklist

b4c0d80

Add new action to build script

d79295b

Add dynamicChecklist workflow

c3c0759

Add notes about checking results as we go

f8f16a9

Add checklist notes

b4a8c42

Add isPassed flag and failing pipeline if falsey

6e8f83e

Changed action path in workflow for testing

47e6817

Testing GH action

b23966c

Fixed checks categories logic

11823b5

Fixed regex capture group

03a601f

Added missing else clause

62fd8a4

Added core import into custom action

a7c94db

Merged checklist actions into single action

b0c8fcb

Reverted testing changes

e4a5f36

Added logic to remove dynamic check from PR description if it's not r…

8f09990

…elevant anymore

sebryu mentioned this pull request Sep 15, 2023

Bespoke PR checklists #24444

Closed

sebryu added 11 commits September 22, 2023 20:29

Merge branch 'main' into Sebryu-DynamicChecklistPOC

51570ba

Added newComponentCategory to authorChecklist, with detection of reac…

d6d5ced

…t component

Merge branch 'main' into Sebryu-DynamicChecklistPOC

53b4ffd

Test commit - testing GH action from current branch - revert later

db354cf

Fixed undefined file name

198bda2

Test commit - testing GH action on separate repo

b35b6b9

Fixed changedFiles filename reference

162c07b

Reading whole file for detecting react component

d80c9b0

Using relative path to files in detectFunction

c2136a6

Using absolute path in detectFunction

d7b0c73

Fixed path in detectFunction

99e431e

sebryu added 3 commits November 3, 2023 21:51

Parallel execution of functions in authorChecklist, some code improve…

c17ee03

…ments

Merge branch 'main' into Sebryu-DynamicChecklistPOC

d29b1d7

Using promiseRaceTo in newComponentCategory in author checklist

86074ed

sebryu commented Nov 3, 2023

View reviewed changes

.github/actions/javascript/authorChecklist/authorChecklist.ts Show resolved Hide resolved

roryabraham requested changes Nov 4, 2023

View reviewed changes

tests/actions/detectReactComponent.test.ts Show resolved Hide resolved

Renamed promiseRaceTo to promiseSome, prettier autofix

c7751da

sebryu force-pushed the Sebryu-DynamicChecklistPOC branch from c6931aa to c7751da Compare November 7, 2023 11:58

roryabraham requested changes Nov 7, 2023

View reviewed changes

sebryu added 3 commits November 8, 2023 20:54

Merge branch 'main' into Sebryu-DynamicChecklistPOC

9007e87

Merge branch 'main' into Sebryu-DynamicChecklistPOC

93efdf0

Merge branch 'main' into Sebryu-DynamicChecklistPOC

b9e9a8c

roryabraham approved these changes Nov 10, 2023

View reviewed changes

roryabraham merged commit 3716368 into Expensify:main Nov 10, 2023
15 of 18 checks passed

melvin-bot bot added the Emergency label Nov 10, 2023

roryabraham removed the Emergency label Nov 10, 2023

OSBotify mentioned this pull request Nov 14, 2023

Deploy Checklist: New Expensify 2023-11-14 #31324

Closed

OSBotify mentioned this pull request Nov 15, 2023

Deploy Checklist: New Expensify 2023-11-15 #31404

Closed

37 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[POC] Dynamic checklist #27532

[POC] Dynamic checklist #27532

sebryu commented Sep 15, 2023

github-actions bot commented Sep 15, 2023 •

edited

Loading

sebryu commented Sep 15, 2023

sebryu commented Nov 3, 2023 •

edited

Loading

roryabraham commented Nov 3, 2023

roryabraham left a comment •

edited

Loading

roryabraham left a comment •

edited

Loading

roryabraham left a comment

sebryu commented Nov 9, 2023

roryabraham commented Nov 10, 2023

melvin-bot bot commented Nov 10, 2023

melvin-bot bot commented Nov 10, 2023

roryabraham commented Nov 10, 2023

OSBotify commented Nov 10, 2023

OSBotify commented Nov 14, 2023

OSBotify commented Nov 15, 2023

OSBotify commented Nov 15, 2023

[POC] Dynamic checklist #27532

[POC] Dynamic checklist #27532

Conversation

sebryu commented Sep 15, 2023

Details

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

github-actions bot commented Sep 15, 2023 • edited Loading

sebryu commented Sep 15, 2023

sebryu commented Nov 3, 2023 • edited Loading

roryabraham commented Nov 3, 2023

roryabraham left a comment • edited Loading

Choose a reason for hiding this comment

roryabraham left a comment • edited Loading

Choose a reason for hiding this comment

roryabraham left a comment

Choose a reason for hiding this comment

sebryu commented Nov 9, 2023

roryabraham commented Nov 10, 2023

melvin-bot bot commented Nov 10, 2023

melvin-bot bot commented Nov 10, 2023

roryabraham commented Nov 10, 2023

OSBotify commented Nov 10, 2023

OSBotify commented Nov 14, 2023

OSBotify commented Nov 15, 2023

OSBotify commented Nov 15, 2023

github-actions bot commented Sep 15, 2023 •

edited

Loading

sebryu commented Nov 3, 2023 •

edited

Loading

roryabraham left a comment •

edited

Loading

roryabraham left a comment •

edited

Loading