Skip to content

Conversation

@MichaelReyes
Copy link
Contributor

Pull Request (PR) Checklist

Thank you for your contribution! Please confirm that you've checked all the boxes below before submitting your PR. Use [x] to check a box, e.g., [x], and make sure there's no space around the brackets.

PR Context

  • Type: (Bug Fix / Feature / Refactor / Regression Fix) Choose one and delete the rest.
  • Issue Link: Redmine Issue
  • Risk Factor: (Low / Medium / High) - Provide a brief explanation of the risk.

Changes

Describe your changes in detail, highlighting the problem it solves or the feature it adds.

[24939] - update wallet information text
[24938] - reset ticket selection on rider change

Checklist for Reviewers

Documentation and Code Quality

  • KDocs Documentation: Are all changes, new functionalities, and classes documented with KDocs?
  • Architectural Patterns: Is there consistent and proper use of architectural patterns (e.g., MVVM, MVP)?

Testing and Reliability

  • Unit Testing: Are there unit tests for all new functionalities and classes?
  • Emulator and Real Device Testing: Has the application been tested on both emulators and real devices to ensure compatibility?

Error Handling and Logging

  • Error Handling: Are errors and exceptions caught and handled gracefully, ensuring the app remains stable?
  • Logging: Is there proper logging in place for critical errors and information, aiding in debugging and monitoring?

Testing Procedure

If applicable, provide steps or commands for testing your changes. This can help reviewers and testers.

Work-in-Progress (WIP)

List any remaining work or areas that need additional focus. This section can be updated as the work progresses.

  • [ ]
  • [ ]

Remember to keep this template updated based on the feedback and evolving project standards.

[24938] - reset ticket selection on rider change
@github-actions
Copy link

✅ Unit tests passed successfully!

Test results are available under the "Artifacts" section of this run in GitHub Actions.

Please ensure the code is reviewed before proceeding with the merge.

Copy link
Contributor

@sg-jsonjuliane sg-jsonjuliane left a comment

Choose a reason for hiding this comment

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

Looks good to me!

@github-actions
Copy link

github-actions bot commented Jan 6, 2026

This pull request is stale because it has been open 5 days with no activity.

@github-actions github-actions bot added the stale No updates, stale PR label Jan 6, 2026
@github-actions
Copy link

github-actions bot commented Jan 6, 2026

✅ Unit tests passed successfully!

Test results are available under the "Artifacts" section of this run in GitHub Actions.

Please ensure the code is reviewed before proceeding with the merge.

@github-actions github-actions bot removed the stale No updates, stale PR label Jan 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants