Skip to content

Navigation Menu

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

Expensify / App Public

Notifications You must be signed in to change notification settings
Fork 3.1k
Star 4.1k

Code
Issues 1k
Pull requests 338
Actions
Projects 2
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Actions
Projects
Security
Insights

Fix a next step when reimbursing#36880

Merged

mountiny merged 3 commits intoExpensify:mainExpensify/App:mainfrom rezkiy37:fix/36878-next-step-when-reimbursingrezkiy37/Expensify:fix/36878-next-step-when-reimbursingCopy head branch name to clipboard

Feb 20, 2024

+11-7

Conversation Commits3 (3)Checks Files changed

Commits

Commits on Feb 20, 2024

use VBBA
rezkiy37
committed
Merge branch 'main' of https://github.com/rezkiy37/Expensify into fix/36878-next-step-when-reimbursing
rezkiy37
committed
rename a var
rezkiy37
committed

Footer

© 2025 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Docs
Contact

You can’t perform that action at this time.