chore: add github files from expo-cli with simplified CI

expo · Dec 29, 2023 · cb397a2 · cb397a2
1 parent dacbbf5
commit cb397a2
Show file tree

Hide file tree

Showing 8 changed files with 247 additions and 0 deletions.
diff --git a/.github/.COMMIT_TEMPLATE b/.github/.COMMIT_TEMPLATE
@@ -0,0 +1,21 @@
+# 🚨🚨ATTENTION🚨🚨
+# Please follow the commit message format below 📝
+#
+# <type>: <description>
+# [optional body]
+# [optional footer]
+# 
+# types: "fix" = patches a bug in the codebase
+# 	 "feat" = introduces new feature to codebase
+#	 "improvement" = improvement without adding a feature or fixing a bug
+#	 various others: "chore" "docs" "style" "refactor" "perf" "test"
+# 
+# Include "BREAKING CHANGE:" at the beginning of the body or footer if your commit introduces a breaking API change
+
+
+
+
+
+
+# Example commit messages @ https://www.conventionalcommits.org/en/v1.0.0-beta.4/#examples
+# Thank you for cooperating, this allows us to auto-generate a fantastic changelog :)
diff --git a/.github/ISSUE_TEMPLATE/bug_report.yml b/.github/ISSUE_TEMPLATE/bug_report.yml
@@ -0,0 +1,52 @@
+name: "\U0001F41B Bug Report in Expo CLI"
+labels: 'needs review'
+description: 'You want to report a reproducible bug or regression in Expo CLI or related tooling.'
+body:
+  - type: markdown
+    attributes:
+      value: "We're looking to keep questions on our forums and bug reports on the GitHub repo. For questions and help using Expo CLI, post in our [community forums](https://forums.expo.dev/c/expo-cli) (log in with your Expo developer account)."
+  - type: markdown
+    attributes:
+      value: Found a bug in the Expo SDK? Open a bug report [here](https://github.com/expo/expo/issues/new?assignees=&labels=needs+review&template=bug_report.yml) instead.
+  - type: markdown
+    attributes:
+      value: Thanks for taking the time to file a bug report! Please fill out this form as completely as possible.
+  - type: markdown
+    attributes:
+      value: If you leave out sections there is a high likelihood your issue will be closed. If you have a question, not a bug report, please post it on our [forums](https://forums.expo.dev/) instead.
+  - type: textarea
+    validations:
+      required: true
+    attributes:
+      label: Summary
+      description: Describe the issue in 1 or 2 sentences
+      placeholder: Clearly describe what the expected behavior is vs. what is actually happening. This should be as short as possible, while still communicating all the necessary information. If your summary is just 'X library/method isn't working', then you need to continue debugging yourself and provide more information.
+  - type: textarea
+    validations:
+      required: true
+    attributes:
+      label: Environment
+      placeholder: Run `npx expo-env-info` and paste the output here
+  - type: input
+    validations:
+      required: true
+    attributes:
+      label: 'Please specify your device/emulator/simulator platform, model and version'
+  - type: textarea
+    validations:
+      required: false
+    attributes:
+      label: Error output
+      placeholder: If you're running into an error message, please run the same command with `EXPO_DEBUG=true <your command here>` and paste output here.
+  - type: textarea
+    validations:
+      required: true
+    attributes:
+      label: Reproducible demo or steps to reproduce from a blank project
+      description: 'This should include as little code as possible, do not simply link your entire project. Sharing a link to a [Snack](https://snack.expo.dev/) is a GREAT way to provide a reproducible demo :) If a reproducible demo, or a complete list of steps from blank project to bug, are not provided, it is very likely your issue will be closed. Read [here more guidance](https://stackoverflow.com/help/mcve).'
+  - type: markdown
+    attributes:
+      value: Please make sure contributors can follow the steps your provided in order to reproduce the bug.
+  - type: markdown
+    attributes:
+      value: "**Realize that it is up to you to debug your code and be as certain as possible that the bug is with Expo, not with your own app.** [Here's an excellent guide to debugging you can follow](https://github.com/expo/fyi/blob/main/manual-debugging.md#how-to-narrow-down-the-source-of-an-error-a-step-by-step-guide-to-good-old-fashioned-manual-debugging)."
diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml
@@ -0,0 +1,11 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Issue with EAS CLI
+    url: https://github.com/expo/eas-cli/issues/new/choose
+    about: Report issues related to eas-cli in the expo/eas-cli repo.
+  - name: Issue with Expo CLI or Expo Config Plugins
+    url: https://github.com/expo/expo/issues/new?labels=needs+review%2CCLI&template=bug_report_cli.yml
+    about: Report issues related to npx expo and the versioned CLI in the expo/expo repo.
+  - name: Expo Developers Discord
+    url: https://chat.expo.dev/
+    about: Join other developers in discussions regarding Expo.
diff --git a/.github/PULL_REQUEST_TEMPLATE b/.github/PULL_REQUEST_TEMPLATE
@@ -0,0 +1,17 @@
+# Why
+
+<!--
+Please describe the motivation for this PR, and link to relevant GitHub issues, forums posts, or feature requests.
+-->
+
+# How
+
+<!--
+How did you build this feature or fix this bug and why?
+-->
+
+# Test Plan
+
+<!--
+Please describe how you tested this change and how a reviewer could reproduce your test, especially if this PR does not include automated tests! If possible, please also provide terminal output and/or screenshots demonstrating your test/reproduction.
+-->
diff --git a/.github/bug_report.yml b/.github/bug_report.yml
@@ -0,0 +1,52 @@
+name: "\U0001F41B Bug Report in Expo CLI"
+labels: 'needs review'
+description: 'You want to report a reproducible bug or regression in Expo CLI or related tooling.'
+body:
+  - type: markdown
+    attributes:
+      value: "We're looking to keep questions on our forums and bug reports on the GitHub repo. For questions and help using Expo CLI, post in our [community forums](https://forums.expo.dev/c/expo-cli) (log in with your Expo developer account)."
+  - type: markdown
+    attributes:
+      value: Found a bug in the Expo SDK? Open a bug report [here](https://github.com/expo/expo/issues/new?assignees=&labels=needs+review&template=bug_report.yml) instead.
+  - type: markdown
+    attributes:
+      value: Thanks for taking the time to file a bug report! Please fill out this form as completely as possible.
+  - type: markdown
+    attributes:
+      value: If you leave out sections there is a high likelihood your issue will be closed. If you have a question, not a bug report, please post it on our [forums](https://forums.expo.dev/) instead.
+  - type: textarea
+    validations:
+      required: true
+    attributes:
+      label: Summary
+      description: Describe the issue in 1 or 2 sentences
+      placeholder: Clearly describe what the expected behavior is vs. what is actually happening. This should be as short as possible, while still communicating all the necessary information. If your summary is just 'X library/method isn't working', then you need to continue debugging yourself and provide more information.
+  - type: textarea
+    validations:
+      required: true
+    attributes:
+      label: Environment
+      placeholder: Run `npx expo-env-info` and paste the output here
+  - type: input
+    validations:
+      required: true
+    attributes:
+      label: 'Please specify your device/emulator/simulator platform, model and version'
+  - type: textarea
+    validations:
+      required: false
+    attributes:
+      label: Error output
+      placeholder: If you're running into an error message, please run the same command with `EXPO_DEBUG=true <your command here>` and paste output here.
+  - type: textarea
+    validations:
+      required: true
+    attributes:
+      label: Reproducible demo or steps to reproduce from a blank project
+      description: 'This should include as little code as possible, do not simply link your entire project. Sharing a link to a [Snack](https://snack.expo.dev/) is a GREAT way to provide a reproducible demo :) If a reproducible demo, or a complete list of steps from blank project to bug, are not provided, it is very likely your issue will be closed. Read [here more guidance](https://stackoverflow.com/help/mcve).'
+  - type: markdown
+    attributes:
+      value: Please make sure contributors can follow the steps your provided in order to reproduce the bug.
+  - type: markdown
+    attributes:
+      value: "**Realize that it is up to you to debug your code and be as certain as possible that the bug is with Expo, not with your own app.** [Here's an excellent guide to debugging you can follow](https://github.com/expo/fyi/blob/main/manual-debugging.md#how-to-narrow-down-the-source-of-an-error-a-step-by-step-guide-to-good-old-fashioned-manual-debugging)."
diff --git a/.github/config.yml b/.github/config.yml
@@ -0,0 +1,11 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Issue with EAS CLI
+    url: https://github.com/expo/eas-cli/issues/new/choose
+    about: Report issues related to eas-cli in the expo/eas-cli repo.
+  - name: Issue with Expo CLI or Expo Config Plugins
+    url: https://github.com/expo/expo/issues/new?labels=needs+review%2CCLI&template=bug_report_cli.yml
+    about: Report issues related to npx expo and the versioned CLI in the expo/expo repo.
+  - name: Expo Developers Discord
+    url: https://chat.expo.dev/
+    about: Join other developers in discussions regarding Expo.
diff --git a/.github/lock.yml b/.github/lock.yml
@@ -0,0 +1,34 @@
+# Configuration for Lock Threads - https://github.com/dessant/lock-threads
+
+# Number of days of inactivity before a closed issue or pull request is locked
+# daysUntilLock: 60
+
+# Skip issues and pull requests created before a given timestamp. Timestamp must
+# follow ISO 8601 (`YYYY-MM-DD`). Set to `false` to disable
+# skipCreatedBefore: false
+
+# Issues and pull requests with these labels will be ignored. Set to `[]` to disable
+# exemptLabels: []
+
+# Label to add before locking, such as `outdated`. Set to `false` to disable
+# lockLabel: outdated
+
+# Comment to post before locking. Set to `false` to disable
+# lockComment: false
+
+# Assign `resolved` as the reason for locking. Set to `false` to disable
+# setLockReason: true
+
+# Limit to only `issues` or `pulls`
+# only: issues
+# Optionally, specify configuration settings just for `issues` or `pulls`
+# issues:
+#   exemptLabels:
+#     - help-wanted
+#   lockLabel: outdated
+
+# pulls:
+#   daysUntilLock: 30
+
+# Repository to extend settings from
+_extends: expo
diff --git a/.github/workflows/packages.yml b/.github/workflows/packages.yml
@@ -0,0 +1,49 @@
+name: Packages
+
+concurrency:
+  group: ${{ github.workflow }}-${{ github.event_name }}-${{ github.ref }}
+  cancel-in-progress: true
+
+on:
+  workflow_dispatch:
+  push:
+    branches: [main]
+  pull_request:
+    types: [opened, synchronize]
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        node: [16.x]
+        package:
+          - electron-adapter
+          - next-adapter
+          - pwa
+          - webpack-config
+    steps:
+      - name: 🏗 Setup repository
+        uses: actions/checkout@v3
+
+      - name: 🏗 Setup Node
+        uses: actions/setup-node@v3
+        with:
+          node-version: ${{ matrix.node }}
+          cache: yarn
+
+      - name: 📦 Install dependencies
+        run: yarn install --frozen-lockfile
+
+      - name: 🛠 Build dependencies
+        run: yarn run build
+
+      - name: 🚨 Lint ${{ matrix.package }}
+        working-directory: packages/${{ matrix.package }}
+        run: yarn run lint
+
+      - name: 🧪 Test ${{ matrix.package }}
+        working-directory: packages/${{ matrix.package }}
+        run: yarn run test
+