Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[NoQA] Web job for the testBuild workflow #13354

Merged
merged 23 commits into from
Dec 16, 2022

Conversation

staszekscp
Copy link
Contributor

@staszekscp staszekscp commented Dec 6, 2022

Details

The PR adds a job to build the web testing app in the testBuild workflow

Fixed Issues

$ GH_LINK
PROPOSAL: GH_LINK_ISSUE(COMMENT)

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:
    • iOS / native
    • Android / native
    • iOS / Safari
    • Android / Chrome
    • MacOS / Chrome
    • 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 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 correct English and 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
    • 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 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 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 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

@staszekscp staszekscp requested a review from a team as a code owner December 6, 2022 09:04
@melvin-bot melvin-bot bot requested review from PauloGasparSv and removed request for a team December 6, 2022 09:04
@melvin-bot
Copy link

melvin-bot bot commented Dec 6, 2022

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

luacmartins
luacmartins previously approved these changes Dec 6, 2022
Copy link
Contributor

@luacmartins luacmartins left a comment

Choose a reason for hiding this comment

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

LGTM but I'd definitely like more eyes since these workflows aren't my strength

@AndrewGable
Copy link
Contributor

Please do not merge - I need to confirm with the infra team this is how we want to set it up.

@PauloGasparSv
Copy link
Contributor

Is this P.R. ready for review? I saw some changes earlier today and no GH issue linked so I was waiting for an update to start reviewing.
Thx for adding people here @luacmartins!

@AndrewGable AndrewGable changed the title Web job for the testBuild workflow [HOLD]Web job for the testBuild workflow Dec 6, 2022
@AndrewGable
Copy link
Contributor

@coleaeason said he would review the infra side of things, thank you @coleaeason ❤️ !!

PULL_REQUEST_NUMBER: ${{ github.event.number }}

- name: Create CloudFront distribution for the PR if needed
run: ./.github/scripts/verifyActions.sh "$PULL_REQUEST_NUMBER"
Copy link
Contributor

Choose a reason for hiding this comment

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

It looks like this is calling the wrong script? should this be the new script you added?

#!/bin/bash
set -e

DISTRIBUTION_ID=$(echo aws cloudfront list-distributions --query "DistributionList.Items[?Origins.Items[?OriginPath=='/web/$1']].Id" --output text)
Copy link
Contributor

Choose a reason for hiding this comment

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

echo likely isn't needed here?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Removed, thank you, I missed this one!


DISTRIBUTION_ID=$(echo aws cloudfront list-distributions --query "DistributionList.Items[?Origins.Items[?OriginPath=='/web/$1']].Id" --output text)

if [[ $(aws cloudfront list-distributions --query "DistributionList.Items[0].Id") != null ]] && [[ $DISTRIBUTION_ID ]] ; then
Copy link
Contributor

Choose a reason for hiding this comment

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

is null a string? null doesn't exist in bash; so i think you mean "null"?

Also can you make the second item explicit? i.e. $DISTRIBUTION_ID != ""?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Actually a string "null" is returned, that's why I was checking it. I've just updated the script by adding the "

if [[ $(aws cloudfront list-distributions --query "DistributionList.Items[0].Id") != null ]] && [[ $DISTRIBUTION_ID ]] ; then
echo "Distribution for PR #$1 already exists! Invalidating cache..."
aws cloudfront create-invalidation --distribution-id $DISTRIBUTION_ID --paths '/'
exit 0;
Copy link
Contributor

Choose a reason for hiding this comment

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

why ;?

exit 0;
else
echo "A new distribution for PR #$1 is being created"
echo $(aws cloudfront create-distribution --origin-domain-name ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com --default-root-object index.html) >> cloudfront.config.json
Copy link
Contributor

Choose a reason for hiding this comment

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

the echo and subprocess isn't needed here. Also why are we writing this to a file? why not:

CLOUDFRONT_CONFIG=$(aws cloudfront create-distribution --origin-domain-name ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com --default-root-object index.html)

echo "A new distribution for PR #$1 is being created"
echo $(aws cloudfront create-distribution --origin-domain-name ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com --default-root-object index.html) >> cloudfront.config.json

CONFIG=$(cat "./cloudfront.config.json")
Copy link
Contributor

Choose a reason for hiding this comment

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

if you do my above suggestion you can delete this line

echo $(aws cloudfront create-distribution --origin-domain-name ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com --default-root-object index.html) >> cloudfront.config.json

CONFIG=$(cat "./cloudfront.config.json")
DISTRIBUTION_ID=$(echo $CONFIG | jq -r .Distribution.Id)
Copy link
Contributor

Choose a reason for hiding this comment

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

nab, you can do:

jq -r .Distribution.Id <<< $CONFIG


CONFIG=$(cat "./cloudfront.config.json")
DISTRIBUTION_ID=$(echo $CONFIG | jq -r .Distribution.Id)
ETAG=$(echo $CONFIG | jq -r .ETag)
Copy link
Contributor

Choose a reason for hiding this comment

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

same here, use a herestring

DISTRIBUTION_ID=$(echo $CONFIG | jq -r .Distribution.Id)
ETAG=$(echo $CONFIG | jq -r .ETag)

echo $CONFIG | jq -r .Distribution.DistributionConfig >> dist.config.json
Copy link
Contributor

Choose a reason for hiding this comment

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

why are we saving a json file here? Can't we just use a bash variable?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

aws cloudfront update-distribution command requires sending a file with the config, that's why I decided to create it


tmp=$(mktemp /tmp/tmp.XXXXXXX)
NEW_ORIGIN_PATH=$(echo "/web/$1")
jq --arg originPath "$NEW_ORIGIN_PATH" '(.Origins.Items[] | select(.OriginPath == "")).OriginPath |= $originPath' dist.config.json > "$tmp" && mv "$tmp" dist.config.json
Copy link
Contributor

Choose a reason for hiding this comment

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

I'm not sure I understand why we need this tmp file?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

As far as I know jq can't edit files, that's why I create a temporary file in order to make a change

@roryabraham
Copy link
Contributor

NAB but I put up a PR here to lint bash scripts in this repo with ShellCheck, and it might be beneficial to make sure that the script you created here is passing ShellCheck using:

npx shellcheck -e SC1091 .github/scripts/createCloudfrontDistribution.sh

@AndrewGable
Copy link
Contributor

Apologies, we believe we are going to go a different direction and use Cloudflare workers instead of Cloudfront as mentioned here: https://expensify.slack.com/archives/C04878MDF34/p1671061957278119

@coleaeason will circle back soon with how this is all going to tie together, thank you for your patience!

Comment on lines 221 to 223
- name: Create CloudFront distribution for the PR if needed
run: ./.github/scripts/createCloudfrontDistribution.sh "$PULL_REQUEST_NUMBER"

Copy link
Contributor

Choose a reason for hiding this comment

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

As Andrew mentioned, we are going to remove Cloudfront form this setup, so you can remove this step.

@@ -0,0 +1,24 @@
#!/bin/bash
Copy link
Contributor

Choose a reason for hiding this comment

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

This can also be removed now

Comment on lines 252 to 257
- name: Get CloudFront URL
id: get_cloudfront_url
run: |
cloudfront_url=$(aws cloudfront list-distributions --query "DistributionList.Items[?Origins.Items[?OriginPath=='/web/$PULL_REQUEST_NUMBER']].DomainName" --output text)
echo "cloudfront_url=$cloudfront_url" >> "$GITHUB_OUTPUT"

Copy link
Contributor

Choose a reason for hiding this comment

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

This can also be removed.

| ![Android](https://api.qrserver.com/v1/create-qr-code/?size=200x200&data=${{fromJson(steps.set_var.outputs.android_paths).html_path}}) | ![iOS](https://api.qrserver.com/v1/create-qr-code/?size=200x200&data=${{fromJson(steps.set_var.outputs.ios_paths).html_path}}) | ![desktop](https://api.qrserver.com/v1/create-qr-code/?size=200x200&data=https://ad-hoc-expensify-cash.s3.amazonaws.com/desktop/$PULL_REQUEST_NUMBER/NewExpensify.dmg) |"
| android :robot: | iOS :apple: | desktop :computer: | web :spider_web: |
| ------------- | ------------- | ------------- | ------------- |
| ${{fromJson(steps.set_var.outputs.android_paths).html_path}} | ${{fromJson(steps.set_var.outputs.ios_paths).html_path}} | https://ad-hoc-expensify-cash.s3.amazonaws.com/desktop/$PULL_REQUEST_NUMBER/NewExpensify.dmg | https://${{steps.get_cloudfront_url.outputs.cloudfront_url}} |
Copy link
Contributor

Choose a reason for hiding this comment

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

The URL now is:

https://<PR_NUMBER>.pr-testing.expensify.com

@staszekscp
Copy link
Contributor Author

@coleaeason Thanks for the info, I've just applied the changes!

@AndrewGable AndrewGable changed the title [HOLD]Web job for the testBuild workflow Web job for the testBuild workflow Dec 16, 2022
Copy link
Contributor

@coleaeason coleaeason left a comment

Choose a reason for hiding this comment

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

LGTM -- Not sure why checks are failing. @AndrewGable ?

@luacmartins
Copy link
Contributor

luacmartins commented Dec 16, 2022

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:
    • iOS / native
    • Android / native
    • iOS / Safari
    • Android / Chrome
    • MacOS / Chrome
    • 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 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 correct English and 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 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 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 have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

N/A these changes only affect GH actions.

Web
Mobile Web - Chrome
Mobile Web - Safari
Desktop
iOS
Android

@luacmartins
Copy link
Contributor

luacmartins commented Dec 16, 2022

@staszekscp we've updated the author checklist. Could you please update your checklist accordingly? You can find the latest checklist in this template

@staszekscp
Copy link
Contributor Author

@luacmartins Done!

@AndrewGable AndrewGable merged commit 6502b73 into Expensify:main Dec 16, 2022
@AndrewGable
Copy link
Contributor

@OSBotify
Copy link
Contributor

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

@staszekscp
Copy link
Contributor Author

staszekscp commented Dec 16, 2022

@AndrewGable @luacmartins @coleaeason The link works, that is cool! Great job guys! https://13354.pr-testing.expensify.com/

I've just noticed something - if the QR code doesn't work, here's the fix: #13673

@github-actions
Copy link
Contributor

Performance Comparison Report 📊

Significant Changes To Duration

There are no entries

Meaningless Changes To Duration

Show entries
Name Duration
runJsBundle 188.067 ms → 196.290 ms (+8.224 ms, +4.4%)
TTI 809.254 ms → 816.485 ms (+7.230 ms, +0.9%)
regularAppStart 0.016 ms → 0.014 ms (-0.001 ms, -9.1%)
nativeLaunch 9.938 ms → 9.862 ms (-0.075 ms, -0.8%)
Show details
Name Duration
runJsBundle Baseline
Mean: 188.067 ms
Stdev: 18.578 ms (9.9%)
Runs: 155 160 161 164 171 171 175 176 180 181 181 182 182 185 185 187 187 189 189 192 193 196 201 203 206 207 209 214 220 240

Current
Mean: 196.290 ms
Stdev: 26.699 ms (13.6%)
Runs: 165 167 167 168 171 171 174 175 175 176 176 176 181 184 185 189 190 193 198 200 210 210 211 213 222 223 223 233 246 253 260
TTI Baseline
Mean: 809.254 ms
Stdev: 39.632 ms (4.9%)
Runs: 745.241686000023 759.3225680000614 761.3042800000403 770.9614069999661 773.341333999997 774.5643909999635 775.2939140000381 776.1683910000138 776.8291070000269 785.4521639999002 787.8009879998863 788.3494990000036 793.8393079999369 797.4548110000324 799.8484179999214 801.8986140000634 803.1177789999638 805.2343820000533 807.6125719998963 817.603371999925 819.5014130000491 820.2955859999638 831.7920280001126 834.7493739998899 835.0498359999619 844.4917109999806 846.7202649998944 871.3239209998865 885.7042880000081 886.0539559999015 909.9574760000687

Current
Mean: 816.485 ms
Stdev: 47.127 ms (5.8%)
Runs: 740.9046000000089 752.9197190001141 755.5218249999452 763.9502059998922 765.8966840000357 774.9468010000419 779.2956050001085 782.5237829999533 788.9277200000361 789.0217589999083 789.5269649999682 795.5592139998917 798.2493129998911 803.8936840000097 805.9184300000779 809.3712249998935 813.4325119999703 813.7246709999163 813.8410179999191 817.6787739999127 822.3978870001156 825.1584139999468 843.5906819999218 850.950482999906 856.1415210000705 864.5186109999195 871.5167219999712 884.4427539999597 892.1100389999337 904.3003450001124 940.788739999989
regularAppStart Baseline
Mean: 0.016 ms
Stdev: 0.001 ms (6.1%)
Runs: 0.014038000022992492 0.014119999948889017 0.014160000020638108 0.014567000092938542 0.014730000169947743 0.014811000088229775 0.015054999850690365 0.015055999858304858 0.01525900000706315 0.015300000086426735 0.015381000004708767 0.015421000076457858 0.015584999928250909 0.015625 0.01566599984653294 0.015666000079363585 0.015746999997645617 0.0157880000770092 0.015828999923542142 0.015868999995291233 0.016032000072300434 0.016112999990582466 0.016194000141695142 0.016357999993488193 0.016398000065237284 0.016561000142246485 0.017130000051110983 0.0174150001257658 0.017578000202775 0.017863000044599175

Current
Mean: 0.014 ms
Stdev: 0.001 ms (4.6%)
Runs: 0.0134680001065135 0.013508999953046441 0.013550000032410026 0.013589999871328473 0.013631000183522701 0.013671999797224998 0.013672000030055642 0.01371199986897409 0.013712999876588583 0.013752999948337674 0.013753999955952168 0.013794000027701259 0.013875999953597784 0.013916000025346875 0.013955999864265323 0.014160000020638108 0.01424099993892014 0.014241999946534634 0.01432300009764731 0.014364000177010894 0.014484999934211373 0.014526000013574958 0.014689000090584159 0.01485200016759336 0.014892000006511807 0.0148930000141263 0.014934000093489885 0.014973999932408333 0.015014000004157424 0.015217999927699566 0.015828000148758292 0.015909999841824174
nativeLaunch Baseline
Mean: 9.938 ms
Stdev: 1.519 ms (15.3%)
Runs: 8 8 8 8 8 8 8 9 9 9 9 9 9 9 9 10 10 10 10 11 11 11 11 11 11 11 11 12 12 12 13 13

Current
Mean: 9.862 ms
Stdev: 1.548 ms (15.7%)
Runs: 8 8 8 8 8 8 9 9 9 9 9 9 9 9 10 10 10 10 10 10 11 11 11 11 11 12 12 13 14

@luacmartins
Copy link
Contributor

Nice! Awesome job @staszekscp!

@OSBotify
Copy link
Contributor

@OSBotify
Copy link
Contributor

🚀 Deployed to staging by @AndrewGable in version: 1.2.42-0 🚀

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

@mountiny mountiny changed the title Web job for the testBuild workflow [NoQA] Web job for the testBuild workflow Dec 20, 2022
@OSBotify
Copy link
Contributor

🚀 Deployed to production by @yuwenmemon in version: 1.2.42-2 🚀

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants