[13604] Run GHA workflow tests on each PR #30975
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Added the first version of GHA workflow running workflow tests on opening and syncing of PRs See: Expensify#13604
runs -> run See: Expensify#13604
Added workflow_dispatch trigger See: Expensify#13604
Added PR event type of edited See: Expensify#13604
…un-workflow-tests-on-pr Run GHA workflow tests on each PR
Added step for Act installation See: Expensify#13604
Added step for Homebrew installation See: Expensify#13604
Updated step for Homebrew installation with post install commands See: Expensify#13604
Added some debug echoes See: Expensify#13604
Found existing Homebrew setup step See: Expensify#13604
Added step for setting the ACT_BINARY env variable See: Expensify#13604
Updated step for setting the ACT_BINARY to use the way proposed by GHA See: Expensify#13604
Updated step for running tests with debug echoes to get into what is the working dir See: Expensify#13604
Updated step for running tests by removing debug echoes See: Expensify#13604
Fixed tests for preDeploy after two of the jobs have been removed See: Expensify#13604
Fixed tests for testBuild after one of the messages have been updated See: Expensify#13604
Fixed tests for cherryPick after the way github token is passed to a step has changed See: Expensify#13604
Fixed tests for platformDeploy after 2 new steps have been added See: Expensify#13604
Fixed tests for finishReleaseCycle after 2 new steps have been added and the way the token is passed has changed See: Expensify#13604
Fixed tests for createNewVersion after new secrets have been added and the way the token is passed has changed See: Expensify#13604
Fixed tests for deploy after new secrets have been added and the way the token is passed has changed See: Expensify#13604
Fixed tests for lint after new steps have been added See: Expensify#13604
Run prettier See: Expensify#13604
Add quotes to satisfy linter See: Expensify#13604
melvin-bot
bot
requested review from
sobitneupane
and removed request for
a team
|
@sobitneupane 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] |
Removed strategy field from gha workflow See: Expensify#13604
|
welp. I'll ask for a volunteer in Slack |
|
hiya! you can assign it to me |
|
This is a test that |
|
The new workflow executes on PR events, when contents of |
| pull_request: | ||
| types: [opened, reopened, edited, synchronize] | ||
| branches-ignore: [staging, production] | ||
| paths: ['.github'] |
There was a problem hiding this comment.
This workflow should have run in this PR also. But I don't see it here.
I think it might be our path. (ref here)
Suggested change
| paths: ['.github'] | |
| paths: ['.github/**'] |
There was a problem hiding this comment.
Yes, you're probably right
Updated the paths field in the workflow with the wildcard to match all files in .github directory and subdirectories See: Expensify#13604
Declares and defines actor value within the test See: Expensify#13604
|
Not sure why these 3 particular tests fail in GHA as all tests pass locally, need to investigate it some more |
…04-run-workflow-tests-on-pr # Conflicts: # .github/workflows/deploy.yml # .github/workflows/finishReleaseCycle.yml
Fixed platformDeploy workflow tests after recent changes in upstream See: Expensify#13604
Fixed authorChecklist workflow tests after recent changes in upstream See: Expensify#13604
Fixed deployBlocker workflow tests after recent changes in upstream See: Expensify#13604
Run prettier See: Expensify#13604
|
Looks good now |
rushatgabhane
approved these changes
Nov 21, 2023
There was a problem hiding this comment.
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 Issuessection 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
Testssection - I verified the steps for Staging and/or Production testing are in the
QA stepssection - 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 verified the steps for local testing are in the
- 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: mWeb Chrome
- iOS: Native
- iOS: mWeb 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.
toggleReportand notonIconClick). - 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 Copylabel 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
- 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.
- 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 usingAvatarhave 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
thisproperly so there are no scoping issues (i.e. foronClick={this.submit}the methodthis.submitshould be bound tothisin the constructor) - Any internal methods bound to
thisare necessary to be bound (i.e. avoidthis.submit = this.submit.bind(this);ifthis.submitis never passed to a component event handler likeonClick) - 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
Avataris modified, I verified thatAvataris 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
ScrollViewcomponent to make it scrollable when more elements are added to the page. - If the
mainbranch was merged into this PR after a review, I tested again and verified the outcome was still expected according to theTeststeps. - I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.
dangrous
previously approved these changes
Nov 22, 2023
There was a problem hiding this comment.
One very not a blocker comment, otherwise looks good. Double checked this still runs well locally as well as on GH. Will let @AndrewGable take a last look!
| @@ -18,7 +18,8 @@ jobs: | |||
| ref: main | |||
| token: ${{ secrets.OS_BOTIFY_TOKEN }} | |||
|
|
|||
| - uses: ./.github/actions/composite/setupGitForOSBotifyApp | |||
| - name: Setup Git for OSBotify | |||
There was a problem hiding this comment.
Suggested change
| - name: Setup Git for OSBotify | |
| - name: Setup git for OSBotify |
NAB - others are lowercase, ideally this should match
Changed step names containing git to have it in lowercase See: Expensify#13604
dangrous
approved these changes
Nov 27, 2023
AndrewGable
approved these changes
Nov 27, 2023
|
✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release. |
53 tasks
|
🚀 Deployed to staging by https://github.com/AndrewGable in version: 1.4.4-0 🚀
|
|
🚀 Deployed to production by https://github.com/mountiny in version: 1.4.4-3 🚀
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Details
Added a new workflow that runs previously added GHA workflow tests on each PR (excluding PRs to
stagingandproduction)Fixed Issues
$ #13604 (comment)
Tests
Offline tests
QA Steps
PR Author Checklist
### Fixed Issuessection aboveTestssectionOffline stepssectionQA stepssectiontoggleReportand notonIconClick)myBool && <MyComponent />.src/languages/*files and using the translation methodWaiting for Copylabel for a copy review on the original GH to get the correct copy.STYLE.md) were followedAvatar, I verified the components usingAvatarare working as expected)/** comment above it */thisare necessary to be bound (i.e. avoidthis.submit = this.submit.bind(this);ifthis.submitis never passed to a component event handler likeonClick)StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG))Avataris modified, I verified thatAvataris working as expected in all cases)ScrollViewcomponent to make it scrollable when more elements are added to the page.mainbranch was merged into this PR after a review, I tested again and verified the outcome was still expected according to theTeststeps.Screenshots/Videos
Android: Native
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari
MacOS: Desktop