[PR #6473] [CLOSED] chore: enable Android / iOS CI #7408

Closed
opened 2026-03-23 23:19:29 +00:00 by mirror · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/AppFlowy-IO/AppFlowy/pull/6473
Author: @LucasXu0
Created: 10/4/2024
Status: Closed

Base: mainHead: ios_ci


📝 Commits (5)

📊 Changes

14 files changed (+187 additions, -178 deletions)

View changed files

.github/workflows/android_ci.yaml (+120 -0)
.github/workflows/android_ci.yaml.bak (+0 -126)
📝 .github/workflows/ios_ci.yaml (+15 -16)
📝 .github/workflows/release.yml (+2 -2)
📝 .github/workflows/rust_ci.yaml (+1 -1)
📝 .github/workflows/rust_coverage.yml (+2 -2)
📝 .github/workflows/tauri2_ci.yaml (+3 -3)
📝 .github/workflows/tauri_ci.yaml (+3 -3)
📝 .github/workflows/tauri_release.yml (+5 -6)
📝 frontend/appflowy_flutter/integration_test/mobile/document/page_style_test.dart (+10 -9)
📝 frontend/appflowy_flutter/integration_test/mobile_runner.dart (+1 -2)
📝 frontend/appflowy_flutter/integration_test/runner.dart (+3 -3)
📝 frontend/appflowy_flutter/integration_test/shared/base.dart (+10 -2)
📝 frontend/appflowy_flutter/packages/appflowy_backend/lib/log.dart (+12 -3)

📄 Description

Feature Preview

Don't merge. It's for testing the GitHub Actions.


PR Checklist

  • My code adheres to AppFlowy's Conventions
  • I've listed at least one issue that this PR fixes in the description above.
  • I've added a test(s) to validate changes in this PR, or this PR only contains semantic changes.
  • All existing tests are passing.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/AppFlowy-IO/AppFlowy/pull/6473 **Author:** [@LucasXu0](https://github.com/LucasXu0) **Created:** 10/4/2024 **Status:** ❌ Closed **Base:** `main` ← **Head:** `ios_ci` --- ### 📝 Commits (5) - [`80a35f1`](https://github.com/AppFlowy-IO/AppFlowy/commit/80a35f1607064465352eb2607f81bc22d857af87) feat: enable ios ci - [`784a811`](https://github.com/AppFlowy-IO/AppFlowy/commit/784a811475abdd5d4328cd14938436a231559662) chore: enable android ci - [`59952a1`](https://github.com/AppFlowy-IO/AppFlowy/commit/59952a1b763a9d4309b1d8680f89dcfa86df4cec) fix: ios integration tests - [`587fed8`](https://github.com/AppFlowy-IO/AppFlowy/commit/587fed883d1c17e9bc58edf50f172a88c8852ea6) fix: page style test - [`2a26903`](https://github.com/AppFlowy-IO/AppFlowy/commit/2a26903c2c7f90b29674337e87ea9add37f28800) fix: ios tests ### 📊 Changes **14 files changed** (+187 additions, -178 deletions) <details> <summary>View changed files</summary> ➕ `.github/workflows/android_ci.yaml` (+120 -0) ➖ `.github/workflows/android_ci.yaml.bak` (+0 -126) 📝 `.github/workflows/ios_ci.yaml` (+15 -16) 📝 `.github/workflows/release.yml` (+2 -2) 📝 `.github/workflows/rust_ci.yaml` (+1 -1) 📝 `.github/workflows/rust_coverage.yml` (+2 -2) 📝 `.github/workflows/tauri2_ci.yaml` (+3 -3) 📝 `.github/workflows/tauri_ci.yaml` (+3 -3) 📝 `.github/workflows/tauri_release.yml` (+5 -6) 📝 `frontend/appflowy_flutter/integration_test/mobile/document/page_style_test.dart` (+10 -9) 📝 `frontend/appflowy_flutter/integration_test/mobile_runner.dart` (+1 -2) 📝 `frontend/appflowy_flutter/integration_test/runner.dart` (+3 -3) 📝 `frontend/appflowy_flutter/integration_test/shared/base.dart` (+10 -2) 📝 `frontend/appflowy_flutter/packages/appflowy_backend/lib/log.dart` (+12 -3) </details> ### 📄 Description <!--- Thank you for submitting a pull request to AppFlowy. The team will dedicate their best efforts to reviewing and approving your pull request. If you have any questions about the project or feedback for us, please join our [Discord](https://discord.gg/wdjWUXXhtw). --> <!--- If your pull request adds a new feature, please drag and drop a video into this section to showcase what you've done! If not, you may delete this section. --> ### Feature Preview Don't merge. It's for testing the GitHub Actions. <!--- List at least one issue here that this PR addresses. If it fixes the issue, please use the [fixes](https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/using-keywords-in-issues-and-pull-requests) keyword to close the issue. For example: fixes https://github.com/AppFlowy-IO/AppFlowy/pull/2106 --> --- <!--- Before you mark this PR ready for review, run through this checklist! --> #### PR Checklist - [ ] My code adheres to [AppFlowy's Conventions](https://docs.appflowy.io/docs/documentation/software-contributions/conventions) - [ ] I've listed at least one issue that this PR fixes in the description above. - [ ] I've added a test(s) to validate changes in this PR, or this PR only contains semantic changes. - [ ] All existing tests are passing. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
mirror 2026-03-23 23:19:29 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
AppFlowy-IO/AppFlowy#7408
No description provided.