-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #3 from fernandatoledo/sonar
Sonar
- Loading branch information
Showing
89 changed files
with
477 additions
and
4,195 deletions.
There are no files selected for viewing
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
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,46 @@ | ||
name: SonarQube analysis | ||
|
||
on: | ||
pull_request: | ||
types: [opened, synchronize] | ||
push: | ||
branches: | ||
- main | ||
- master | ||
- staging | ||
- qa | ||
- development | ||
|
||
env: | ||
SONAR_PROJECT: myapp-delete | ||
|
||
jobs: | ||
sonar: | ||
runs-on: ubuntu-latest | ||
steps: | ||
- name: 📦 Checkout project repo | ||
uses: actions/checkout@v3 | ||
with: | ||
fetch-depth: 0 | ||
|
||
- name: 📦 Setup Node + PNPM + install deps | ||
uses: ./.github/actions/setup-node-pnpm-install | ||
|
||
- name: Run Tests | ||
run: export NODE_OPTIONS=--experimental-vm-modules && pnpm test:ci | ||
|
||
- name: SonarQube Scan | ||
uses: sonarsource/sonarqube-scan-action@master | ||
env: | ||
SONAR_TOKEN: ${{ secrets.SONAR_TOKEN }} | ||
SONAR_HOST_URL: ${{ secrets.SONAR_URL }} | ||
with: | ||
args: > | ||
-Dsonar.sonar.sources=./src | ||
-Dsonar.qualitygate.wait=true | ||
-Dsonar.projectBaseDir=. | ||
-Dsonar.verbose=false | ||
-Dsonar.projectKey=${{ secrets.SONAR_PROJECT }} | ||
-Dsonar.sonar.sourceEncoding=UTF-8 | ||
-Dsonar.javascript.lcov.reportPaths=coverage/lcov.info | ||
-Dsonar.coverage.exclusions=**/storage/**,**/**.config.js,**/*.test.tsx,**/icons/** |
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,38 @@ | ||
## Distribute using Expo Application Services | ||
|
||
To be able to use Expo Application Services to upload your app to App Store and Google Play Store there are some configurations that need to be done on your side. | ||
|
||
### Google Play Store | ||
|
||
The first submission of the app needs to be performed manually. Learn more: https://expo.fyi/first-android-submission. Only after having a valid version submitted you can submit automatically using EAS. | ||
|
||
To submit an app to google play store you will have to follow the steps in [Uploading a Google Service Account Key for Play Store Submissions with EAS](https://github.com/expo/fyi/blob/main/creating-google-service-account.md) guide, its super detailed and should not take you much time. | ||
|
||
Once you've completed the guide you'll be able to submit to the store your EAS builds using the following command: | ||
|
||
`eas submit --platform android` | ||
|
||
### AppStore | ||
|
||
1. Ensure your credentials are configured correctly in EAS. You can do this by running the following command in your terminal: | ||
|
||
`eas credentials` | ||
|
||
Follow the prompts to authenticate and select your Apple Developer account. | ||
|
||
2. Build your app using Expo and EAS: | ||
|
||
`eas build --platform ios` | ||
|
||
This command initiates the build process for iOS using Expo Application Services. | ||
|
||
3. Submit Your Build to the App Store | ||
Once your build is complete, you can submit it to the App Store using the following command: | ||
|
||
`eas submit --platform ios` | ||
|
||
This command will handle the submission of your build to the App Store using the credentials and configuration you provided. | ||
|
||
### Additional Resources | ||
|
||
For more detailed instructions on setting up your Apple Developer account, certificates, and provisioning profiles, refer to the [EAS Submits](https://docs.expo.dev/submit/introduction/) docs. |
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
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
Binary file not shown.
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
Oops, something went wrong.