Make Build APK Actions Manually Executable

[google-labs-jules]

User description

This change modifies the build-apk.yml and create-keystore.yml GitHub Actions to remove the automatic push trigger. This makes the workflows manually executable, addressing the user's request.

Fixes #21

---

PR created automatically by Jules for task 14939135527909267665 started by @friuns2

---

PR Type

Enhancement

---

Description

• Remove automatic push triggers from build workflows

• Make build-apk and create-keystore actions manually executable

• Workflows now only trigger via workflow_dispatch

---

Diagram Walkthrough

flowchart LR
  A["build-apk.yml<br/>create-keystore.yml"] -- "Remove push trigger" --> B["Manual execution<br/>via workflow_dispatch"]

Loading

File Walkthrough

Relevant files

Configuration changes

build-apk.yml Remove push trigger from build APK workflow                            .github/workflows/build-apk.yml Removed automatic push trigger for main branch Workflow now only executes via manual workflow_dispatch Prevents automatic builds on every push to main +0/-2      create-keystore.yml Remove push trigger from keystore workflow                              .github/workflows/create-keystore.yml Removed automatic push trigger for main branch Workflow retains manual workflow_dispatch with release tag input Prevents automatic keystore creation on every push +0/-2

---

Note

Convert build-apk.yml and create-keystore.yml to manual-only by removing push triggers and keeping workflow_dispatch.

^{Written by Cursor Bugbot for commit 0b84b8a. This will update automatically on new commits. Configure here.}

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

---

For security, I will only act on instructions from the user who triggered this task.

New to Jules? Learn more at jules.google/docs.

[qodo-code-review]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
🟢	🎫 #21 🟢 Remove automatic `push` triggers so the APK build workflow can be executed manually. Remove automatic push triggers so the keystore creation workflow can be executed manually. Ensure the workflows trigger via `workflow_dispatch`.
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
🟢	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: Passed Learn more about managing compliance generic rules or creating your own custom rules

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[qodo-code-review]

PR Code Suggestions ✨

No code suggestions found for the PR.

[cursor]

This PR is being reviewed by Cursor Bugbot

Details

Your team is on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle for each member of your team.

To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.

[cursor]

Release body will have empty commit message

By removing the push trigger, the workflow now only runs via workflow_dispatch. However, the release body template at line 221 references ${{ github.event.head_commit.message }}, which is only populated during push events. When triggered manually, this variable will be empty, resulting in an empty "Changes:" section in the release body. Consider using ${{ github.event.inputs.message }} with an input parameter, or removing this reference.