Skip to content

Conversation

@iangmaia
Copy link
Contributor

@iangmaia iangmaia commented Feb 6, 2024

This PR adapts the Dangerfile to the latest Dangermattic version, using newly added plugins, adapting the code as needed and implementing a few improvements.

The main changes:

  • Improvements to the Rubocop check call
  • Added Release Notes / Store strings check
  • Added check for translations being changed only on the release branch
  • Added check on the internal release notes being changed
  • Use github_utils plugin instead of locally declared functions
  • Added message report when we're skipping checks due to the Releases label
  • Use officially distributed danger-dangermattic Gem

Testing

The main validation is to make sure CI is 🟢.

To run Danger yourself:

  1. Checkout this branch
  2. Run bundle install
  3. Run:
DANGER_GITHUB_API_TOKEN=<github_token> bundle exec danger pr <PR_URL>

You should get in the console the same errors / warnings reported in the PR.

@iangmaia iangmaia self-assigned this Feb 6, 2024
@wpmobilebot
Copy link
Contributor

wpmobilebot commented Feb 6, 2024

WordPress📲 You can test the changes from this Pull Request in WordPress by scanning the QR code below to install the corresponding build.
App NameWordPress WordPress
FlavorJalapeno
Build TypeDebug
Versionpr20132-49f63b4
Commit49f63b4
Direct Downloadwordpress-prototype-build-pr20132-49f63b4.apk
Note: Google Login is not supported on these builds.

@wpmobilebot
Copy link
Contributor

wpmobilebot commented Feb 6, 2024

Jetpack📲 You can test the changes from this Pull Request in Jetpack by scanning the QR code below to install the corresponding build.
App NameJetpack Jetpack
FlavorJalapeno
Build TypeDebug
Versionpr20132-49f63b4
Commit49f63b4
Direct Downloadjetpack-prototype-build-pr20132-49f63b4.apk
Note: Google Login is not supported on these builds.

@iangmaia iangmaia force-pushed the iangmaia/dangermattic-update branch 2 times, most recently from ddcb6fd to 78226e9 Compare February 6, 2024 19:54
@iangmaia iangmaia force-pushed the iangmaia/dangermattic-update branch from 78226e9 to 1ecc225 Compare February 8, 2024 12:49
@iangmaia iangmaia marked this pull request as ready for review February 8, 2024 14:54
@peril-wordpress-mobile
Copy link

Warnings
⚠️ PR is not assigned to a milestone.

Generated by 🚫 dangerJS

@dangermattic
Copy link
Collaborator

1 Warning
⚠️ PR is not assigned to a milestone.

Generated by 🚫 Danger

@iangmaia iangmaia requested a review from a team February 8, 2024 15:53
@iangmaia iangmaia requested a review from mokagio February 13, 2024 18:48
Copy link
Contributor

@mokagio mokagio left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approving to unblock. The same comments from the Pocket Casts iOS PR apply here, Automattic/pocket-casts-ios#1418 (review), but none of them were blocking.

# Add entries for `screenshot_*.txt` files as well
Dir.glob('screenshot_*.txt', base: metadata_folder).sort.each do |screenshot_file|
key = "play_store_#{File.basename(screenshot_file, '.txt')}".to_sym
key = :"play_store_#{File.basename(screenshot_file, '.txt')}"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

TIL

@iangmaia iangmaia merged commit c548dee into trunk Feb 14, 2024
@iangmaia iangmaia deleted the iangmaia/dangermattic-update branch February 14, 2024 15:59
mokagio added a commit that referenced this pull request Dec 2, 2025
This Danger check was out of place as
`WordPress/src/main/res/values/strings.xml` is the source of truth for
localizations.

Unlike in Apple projects, where we use `genstrings` to find localized
strings in the codebase to assemble the `strings` file, in Android, as
far as I understand, `<app>/src/main/res/valudes/strings.xml` is the
source of truth.

I believe this check ended up in `Dangerfile` accidentally. It was
introduced in
#20132.
The update was done across our suite of apps, see for example
woocommerce/woocommerce-android#10692 and
woocommerce/woocommerce-ios#11926. Given I
couldn't find a comment explicitly about adopting this check, I guess
neither @iangmaia nor myself notice the same pattern as iOS was adopted
in the Android repo.

To reinforce the idea that this check is out of place, notice that
WooCommerce Android does not implement the check. _Of course, it could
be that WooCommerce is wrong, but lacking code to update `strings.xml`
as part of the code freeze process, that explanation is not satisfying._
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants