Skip to content

[NoQA] Add IdentityDot account steps to expert contributor onboarding/offboarding checklist#84335

Merged
fukawi2 merged 2 commits intomainfrom
add-identitydot-onboarding-checklist
Mar 6, 2026
Merged

[NoQA] Add IdentityDot account steps to expert contributor onboarding/offboarding checklist#84335
fukawi2 merged 2 commits intomainfrom
add-identitydot-onboarding-checklist

Conversation

@mountiny
Copy link
Contributor

@mountiny mountiny commented Mar 5, 2026 •
edited
Loading

Explanation of Change

Adds IdentityDot account creation and deletion as Ring0 checklist items in the expert contributor onboarding/offboarding issue template. This ensures that when onboarding an expert contributor, a Ring0 member creates an IdentityDot account, and when offboarding, the account is deleted.

We started to create IdentityDot accounts for the expert contributors, but the checklist was not updated to reflect that

Fixed Issues

$ N/A

Tests

  • Verify that no errors appear in the JS console

N/A - this is a template-only change with no runtime impact.

Offline tests

N/A

QA Steps

[No QA]

  • 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: mWeb Chrome
    • iOS: Native
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • 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 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 used JaimeGPT to get English > Spanish translation. I then posted it 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 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)
    • 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.ts 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 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(theme.componentBG))
  • If new assets were added or existing ones were modified, I verified that:
    • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
    • The assets load correctly across all supported platforms.
  • 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 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.
  • I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user 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.

Screenshots/Videos

Android: Native
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari

@mountiny
Add IdentityDot account steps to expert contributor onboarding/offboa…
5bbdff4 
…rding checklist

Ring0 now has checklist items to create an IdentityDot account when
onboarding and delete it when offboarding expert contributors.

Made-with: Cursor
@mountiny mountiny marked this pull request as ready for review March 5, 2026 23:37
@mountiny mountiny requested a review from a team as a code owner March 5, 2026 23:37
@mountiny
Copy link
Contributor Author

mountiny commented Mar 5, 2026

We started to create IdentityDot accounts for the expert contributors, but the checklist was not updated to reflect that

@melvin-bot melvin-bot bot requested review from fukawi2 and lakchote and removed request for a team March 5, 2026 23:38
@melvin-bot
Copy link

melvin-bot bot commented Mar 5, 2026

@lakchote @fukawi2 One of you needs to 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]

fukawi2
fukawi2 approved these changes Mar 6, 2026
View reviewed changes
Copy link
Contributor

@fukawi2 fukawi2 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No Melvin, I don't think I will thanks....

@fukawi2 fukawi2 merged commit b6d288d into main Mar 6, 2026
14 of 17 checks passed
@fukawi2 fukawi2 deleted the add-identitydot-onboarding-checklist branch March 6, 2026 00:05
@github-actions github-actions bot mentioned this pull request Mar 6, 2026
Closed
@OSBotify OSBotify mentioned this pull request Mar 6, 2026
Closed
92 tasks
@OSBotify
Copy link
Contributor

OSBotify commented Mar 6, 2026

🚀 Deployed to staging by https://github.com/fukawi2 in version: 9.3.32-0 🚀

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

@IuliiaHerets
Copy link

IuliiaHerets commented Mar 6, 2026

Hi @mountiny. Any QA steps here?

@mountiny mountiny changed the title Add IdentityDot account steps to expert contributor onboarding/offboarding checklist [NoQA] Add IdentityDot account steps to expert contributor onboarding/offboarding checklist Mar 6, 2026
@mountiny
Copy link
Contributor Author

mountiny commented Mar 6, 2026

NoQA, sorry

@OSBotify
Copy link
Contributor

OSBotify commented Mar 6, 2026

🚀 Deployed to production by https://github.com/blimpich in version: 9.3.32-3 🚀

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@fukawi2 fukawi2 fukawi2 approved these changes

@lakchote lakchote Awaiting requested review from lakchote

Assignees

@mountiny mountiny

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@mountiny @OSBotify @IuliiaHerets @fukawi2