From dca95e758d515c73db325e8198046b3516b7663f Mon Sep 17 00:00:00 2001 From: Jorge Martin Espinosa Date: Wed, 25 Mar 2026 12:28:55 +0100 Subject: [PATCH] Add some instructions for features to the community PR notice message (#6465) --- .github/workflows/fork-pr-notice.yml | 1 + 1 file changed, 1 insertion(+) diff --git a/.github/workflows/fork-pr-notice.yml b/.github/workflows/fork-pr-notice.yml index 2b0431003a..af3e4a3006 100644 --- a/.github/workflows/fork-pr-notice.yml +++ b/.github/workflows/fork-pr-notice.yml @@ -29,6 +29,7 @@ jobs: repo: context.repo.repo, body: `Thank you for your contribution! Here are a few things to check in the PR to ensure it's reviewed as quickly as possible: + - If your pull request adds a feature or modifies the UI, this should have an equivalent pull request in the [Element X iOS repo](https://github.com/element-hq/element-x-ios) unless it only affects an Android-only behaviour or is behind a disabled feature flag, since we need parity in both clients to consider a feature done. It will also need to be approved by our product and design teams before being merged, so it's usually a good idea to discuss the changes in a Github issue first and then start working on them once the approach has been validated. - Your branch should be based on \`origin/develop\`, at least when it was created. - The title of the PR will be used for release notes, so it needs to describe the change visible to the user. - The test pass locally running \`./gradlew test\`.