Update and rename Invite-Employees.md to Invite.Members.md #28276

NicMendonca · 2023-09-26T18:15:18Z

https://github.com/Expensify/Expensify/issues/311410

Details

Help doc resource

Fixed Issues

https://github.com/Expensify/Expensify/issues/311410

$
PROPOSAL:

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

Expensify/Expensify#311410

github-actions · 2023-09-26T18:15:37Z

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

melvin-bot · 2023-09-26T18:15:56Z

@jasperhuangg 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]

jasperhuangg

few minor changes, good job!

jasperhuangg · 2023-09-27T00:14:18Z

docs/articles/expensify-classic/getting-started/Invite.Members.md

+
+## Inviting Members Manually
+
+Navigate to **Settings > Policies > Group > *Policy Name* > People** - then click Invite and enter the invitee's email address.


It looks like we don't want "Policy Name" to be bolded. Here's how it looks in the Google Doc:

And here's how the markdown looks right now:

Navigate to Settings > Policies > Group > Policy Name > People - then click Invite and enter the invitee's email address.

This should fix it!

Suggested change

Navigate to **Settings > Policies > Group > *Policy Name* > People** - then click Invite and enter the invitee's email address.

Navigate to **Settings > Policies > Group >** *Policy Name* **> People** - then click Invite and enter the invitee's email address.

jasperhuangg · 2023-09-27T00:15:12Z

docs/articles/expensify-classic/getting-started/Invite.Members.md

+
+## Inviting Members to a Policy in Bulk 
+
+Navigate to **Settings > Policies > Group > *Policy Name* > People** - then click Invite and enter all of the email addresses separated by comma. Indicate whether you want them to be an Employee, Admin, or Auditor on the policy.


Same as earlier

Suggested change

Navigate to **Settings > Policies > Group > *Policy Name* > People** - then click Invite and enter all of the email addresses separated by comma. Indicate whether you want them to be an Employee, Admin, or Auditor on the policy.

Navigate to **Settings > Policies > Group >** *Policy Name* **> People** - then click Invite and enter all of the email addresses separated by comma. Indicate whether you want them to be an Employee, Admin, or Auditor on the policy.

jasperhuangg · 2023-09-27T00:15:55Z

docs/articles/expensify-classic/getting-started/Invite.Members.md

+
+You have the ability to invite your colleagues to join your Expensify policy by sharing a unique Policy Joining Link. You can use this link as many times as necessary to invite multiple users through various communication methods such as internal emails, chats, text messages, and more.
+
+To find your unique link, simply go to **Settings > Policies > Group > *Policy Name* > People**. It's easily accessible from there.


Suggested change

To find your unique link, simply go to **Settings > Policies > Group > *Policy Name* > People**. It's easily accessible from there.

To find your unique link, simply go to **Settings > Policies > Group >** *Policy Name* **> People**. It's easily accessible from there.

jasperhuangg · 2023-09-27T00:16:17Z

docs/articles/expensify-classic/getting-started/Invite.Members.md

+Any Policy Admin can add users to a Group policy using any of the above methods.
+
+## How can I customize an invite message? 
+Under **Settings > Policies > Group > *Policy Name* > People > Invite** you can enter a custom message you'd like users to receive in their invitation email.


Suggested change

Under **Settings > Policies > Group > *Policy Name* > People > Invite** you can enter a custom message you'd like users to receive in their invitation email.

Under **Settings > Policies > Group >** *Policy Name* **> People > Invite** you can enter a custom message you'd like users to receive in their invitation email.

jasperhuangg · 2023-09-27T00:17:28Z

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

@NicMendonca Do you mind commenting this in the PR?

NicMendonca · 2023-09-27T14:48:52Z

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

Updating "policy" to workspace, and "users/employees" to "members"

NicMendonca

updating policies to workspaces, and employees/ users to members as per new guidelines

rushatgabhane

@NicMendonca requesting changes

rushatgabhane · 2023-09-29T15:01:37Z

docs/articles/expensify-classic/getting-started/Invite.Members.md

@@ -0,0 +1,62 @@
+---
+title: Invite Members
+description: Invite Members


I don't have a suggestion, but could we improve this description? It'll be shown in google search results.

going to cc my pal @CherylWalsh who was my marketing reviewer! Do we need to change this?

So I think we want to make sure we're applying good descriptions to all help site pages. It's both beneficial for SEO purposes and provides a user with additional details when looking at the page listed in search results.

yes, we need to change this - context here https://expensify.slack.com/archives/C02QSAC6BJ8/p1695970001229149?thread_ts=1695962329.762109&cid=C02QSAC6BJ8

But I am not good at marketing 😂

rushatgabhane · 2023-09-29T15:02:23Z

docs/articles/expensify-classic/getting-started/Invite.Members.md

@@ -0,0 +1,62 @@
+---


could you please re-name this file to Invite-Members.md?

replace the dot . with a dash -

updating description and file name

NicMendonca

desc & title change

rushatgabhane · 2023-09-29T16:34:42Z

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 tests pass on all platforms & I tested again on:
- Android / native
- Android / Chrome
- iOS / native
- iOS / Safari
- MacOS / Chrome / Safari
- MacOS / Desktop
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 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
- 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 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)
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
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
- 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 reviewer checklist, including those that don't apply to this PR.

rushatgabhane

LGTM

melvin-bot · 2023-09-29T16:36:06Z

@pecanoro 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 · 2023-09-29T16:36:10Z

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

An E/App issue has been created to issue payment here: #28510.

docs/articles/expensify-classic/getting-started/Invite-Members.md

fixed typos/ grammar error

NicMendonca

fixed typos/ grammar error

docs/articles/expensify-classic/getting-started/Invite-Members.md

jasperhuangg

docs/articles/expensify-classic/getting-started/Invite-Members.md

pecanoro · 2023-10-05T04:51:35Z

@NicMendonca You need to complete every checkbox in the list in the description in order for us to be able to merge, please!

docs/articles/expensify-classic/getting-started/Invite-Members.md

Co-authored-by: Sonia Liapounova <[email protected]>

cloudflare-workers-and-pages · 2023-10-05T13:51:56Z

Deploying with Cloudflare Pages

Latest commit:	`3c7849c`
Status:	🚫 Build failed.

View logs

pecanoro · 2023-10-10T08:11:27Z

@NicMendonca friendly bump! What do you think about the suggestions?

Co-authored-by: Sonia Liapounova <[email protected]>

OSBotify · 2023-10-11T13:02:16Z

✋ 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-10-13T21:57:35Z

🚀 Deployed to production by https://github.com/jasperhuangg in version: 1.3.83-11 🚀

platform	result
🤖 android 🤖	skipped 🚫
🖥 desktop 🖥	skipped 🚫
🍎 iOS 🍎	skipped 🚫
🕸 web 🕸	skipped 🚫

OSBotify · 2023-10-13T22:09:38Z

🚀 Deployed to production by https://github.com/jasperhuangg in version: 1.3.83-11 🚀

platform	result
🤖 android 🤖	skipped 🚫
🖥 desktop 🖥	skipped 🚫
🍎 iOS 🍎	skipped 🚫
🕸 web 🕸	skipped 🚫

OSBotify · 2023-10-13T22:25:51Z

🚀 Deployed to production by https://github.com/jasperhuangg in version: 1.3.83-11 🚀

platform	result
🤖 android 🤖	skipped 🚫
🖥 desktop 🖥	skipped 🚫
🍎 iOS 🍎	skipped 🚫
🕸 web 🕸	skipped 🚫

OSBotify · 2023-10-13T23:01:16Z

🚀 Deployed to production by https://github.com/jasperhuangg in version: 1.3.83-11 🚀

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

Update and rename Invite-Employees.md to Invite.Members.md

c4b819d

Expensify/Expensify#311410

NicMendonca requested a review from a team as a code owner September 26, 2023 18:15

NicMendonca self-assigned this Sep 26, 2023

melvin-bot bot requested review from jasperhuangg and removed request for a team September 26, 2023 18:15

jasperhuangg requested changes Sep 27, 2023

View reviewed changes

Update Invite.Members.md

5fae13c

Updating "policy" to workspace, and "users/employees" to "members"

NicMendonca commented Sep 28, 2023

View reviewed changes

peterdbarkerUK requested a review from rushatgabhane September 29, 2023 06:41

rushatgabhane suggested changes Sep 29, 2023

View reviewed changes

Update and rename Invite.Members.md to Invite-Members.md

e7f04c9

updating description and file name

NicMendonca commented Sep 29, 2023

View reviewed changes

rushatgabhane approved these changes Sep 29, 2023

View reviewed changes

melvin-bot bot requested a review from pecanoro September 29, 2023 16:36

melvin-bot bot mentioned this pull request Sep 29, 2023

Payment issue for E/App PR#28276 #28510

Closed

pecanoro requested changes Oct 2, 2023

View reviewed changes

docs/articles/expensify-classic/getting-started/Invite-Members.md Outdated Show resolved Hide resolved

docs/articles/expensify-classic/getting-started/Invite-Members.md Outdated Show resolved Hide resolved

Update Invite-Members.md

82551e0

fixed typos/ grammar error

NicMendonca commented Oct 2, 2023

View reviewed changes

jasperhuangg requested changes Oct 2, 2023

View reviewed changes

docs/articles/expensify-classic/getting-started/Invite-Members.md Outdated Show resolved Hide resolved

jasperhuangg previously approved these changes Oct 4, 2023

View reviewed changes

sonialiap reviewed Oct 5, 2023

View reviewed changes

docs/articles/expensify-classic/getting-started/Invite-Members.md Outdated Show resolved Hide resolved

sonialiap reviewed Oct 5, 2023

View reviewed changes

docs/articles/expensify-classic/getting-started/Invite-Members.md Outdated Show resolved Hide resolved

sonialiap reviewed Oct 5, 2023

View reviewed changes

docs/articles/expensify-classic/getting-started/Invite-Members.md Outdated Show resolved Hide resolved

sonialiap reviewed Oct 5, 2023

View reviewed changes

docs/articles/expensify-classic/getting-started/Invite-Members.md Outdated Show resolved Hide resolved

Update docs/articles/expensify-classic/getting-started/Invite-Members.md

a25982b

Co-authored-by: Sonia Liapounova <[email protected]>

NicMendonca dismissed jasperhuangg’s stale review via a25982b October 5, 2023 13:51

Update docs/articles/expensify-classic/getting-started/Invite-Members.md

578fd21

Co-authored-by: Sonia Liapounova <[email protected]>

NicMendonca and others added 2 commits October 10, 2023 07:29

Update docs/articles/expensify-classic/getting-started/Invite-Members.md

72cbab0

Co-authored-by: Sonia Liapounova <[email protected]>

Update docs/articles/expensify-classic/getting-started/Invite-Members.md

3c7849c

Co-authored-by: Sonia Liapounova <[email protected]>

pecanoro approved these changes Oct 11, 2023

View reviewed changes

pecanoro merged commit d59cc1e into main Oct 11, 2023
19 of 47 checks passed

pecanoro deleted the NicMendonca-patch-1 branch October 11, 2023 12:56

mountiny mentioned this pull request Oct 12, 2023

Deploy Checklist: New Expensify 2023-10-12 #29417

Closed

97 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Update and rename Invite-Employees.md to Invite.Members.md #28276

Update and rename Invite-Employees.md to Invite.Members.md #28276

NicMendonca commented Sep 26, 2023 •

edited

Loading

github-actions bot commented Sep 26, 2023 •

edited

Loading

melvin-bot bot commented Sep 26, 2023

jasperhuangg left a comment

jasperhuangg Sep 27, 2023

jasperhuangg Sep 27, 2023

jasperhuangg Sep 27, 2023

jasperhuangg Sep 27, 2023

jasperhuangg commented Sep 27, 2023

NicMendonca commented Sep 27, 2023

NicMendonca left a comment

rushatgabhane left a comment

rushatgabhane Sep 29, 2023

NicMendonca Sep 29, 2023

rushatgabhane Sep 29, 2023 •

edited

Loading

NicMendonca Sep 29, 2023

rushatgabhane Sep 29, 2023

NicMendonca left a comment

rushatgabhane commented Sep 29, 2023 •

edited

Loading

rushatgabhane left a comment

melvin-bot bot commented Sep 29, 2023

melvin-bot bot commented Sep 29, 2023

NicMendonca left a comment

jasperhuangg left a comment

pecanoro commented Oct 5, 2023

cloudflare-workers-and-pages bot commented Oct 5, 2023 •

edited

Loading

pecanoro commented Oct 10, 2023

OSBotify commented Oct 11, 2023

OSBotify commented Oct 13, 2023

OSBotify commented Oct 13, 2023

OSBotify commented Oct 13, 2023

OSBotify commented Oct 13, 2023


		## Inviting Members Manually

		Navigate to *Settings > Policies > Group > Policy Name* > People** - then click Invite and enter the invitee's email address.


		## Inviting Members to a Policy in Bulk

		Navigate to *Settings > Policies > Group > Policy Name* > People** - then click Invite and enter all of the email addresses separated by comma. Indicate whether you want them to be an Employee, Admin, or Auditor on the policy.


		You have the ability to invite your colleagues to join your Expensify policy by sharing a unique Policy Joining Link. You can use this link as many times as necessary to invite multiple users through various communication methods such as internal emails, chats, text messages, and more.

		To find your unique link, simply go to *Settings > Policies > Group > Policy Name* > People**. It's easily accessible from there.

	Under *Settings > Policies > Group > Policy Name* > People > Invite** you can enter a custom message you'd like users to receive in their invitation email.
	Under Settings > Policies > Group > Policy Name > People > Invite you can enter a custom message you'd like users to receive in their invitation email.

Update and rename Invite-Employees.md to Invite.Members.md #28276

Update and rename Invite-Employees.md to Invite.Members.md #28276

Conversation

NicMendonca commented Sep 26, 2023 • edited Loading

Details

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

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

melvin-bot bot commented Sep 26, 2023

jasperhuangg left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

jasperhuangg commented Sep 27, 2023

NicMendonca commented Sep 27, 2023

NicMendonca left a comment

Choose a reason for hiding this comment

rushatgabhane left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

rushatgabhane Sep 29, 2023 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

NicMendonca left a comment

Choose a reason for hiding this comment

rushatgabhane commented Sep 29, 2023 • edited Loading

Reviewer Checklist

rushatgabhane left a comment

Choose a reason for hiding this comment

melvin-bot bot commented Sep 29, 2023

melvin-bot bot commented Sep 29, 2023

NicMendonca left a comment

Choose a reason for hiding this comment

jasperhuangg left a comment

Choose a reason for hiding this comment

pecanoro commented Oct 5, 2023

cloudflare-workers-and-pages bot commented Oct 5, 2023 • edited Loading

Deploying with Cloudflare Pages

pecanoro commented Oct 10, 2023

OSBotify commented Oct 11, 2023

OSBotify commented Oct 13, 2023

OSBotify commented Oct 13, 2023

OSBotify commented Oct 13, 2023

OSBotify commented Oct 13, 2023

NicMendonca commented Sep 26, 2023 •

edited

Loading

github-actions bot commented Sep 26, 2023 •

edited

Loading

rushatgabhane Sep 29, 2023 •

edited

Loading

rushatgabhane commented Sep 29, 2023 •

edited

Loading

cloudflare-workers-and-pages bot commented Oct 5, 2023 •

edited

Loading