Enable Dangermattic strings guardrail#22991
Conversation
|
|
|
|
There was a problem hiding this comment.
Pull request overview
Updates the repo’s Danger setup to use danger-dangermattic v1.3.x and turns on its Android strings “existing strings must not be modified” guardrail (with an escape hatch label).
Changes:
- Bump
danger-dangermatticfrom~> 1.2to~> 1.3(and update the lockfile accordingly). - Enable
android_strings_checker.check_existing_strings_not_modifiedinDangerfile, skipped when the PR has theAllow String Modificationslabel.
Reviewed changes
Copilot reviewed 2 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
Gemfile.lock |
Locks danger-dangermattic to 1.3.0 and updates the danger dependency to match. |
Gemfile |
Updates the Bundler dependency constraint to danger-dangermattic ~> 1.3. |
Dangerfile |
Adds the Android strings guardrail check, with a label-based opt-out. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
GitHub failed on my end when I approved an hour ago, and I didn't realize it went through and ended up approving again now. Sorry about that! |
Dangermattic 1.3.0 includes the Android strings API needed to flag in-place edits to existing translatable strings. Wire it into Danger while keeping release-process PRs skipped and allowing the explicit bypass label for intentional edits. --- Generated with the help of Codex, https://openai.com/codex Co-Authored-By: Codex GPT-5 <noreply@openai.com>
f4761e5 to
dc8c5dc
Compare


Updates
danger-dangermatticto 1.3.0 and enables its Android strings guardrail.