-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[TEST] Please ignore, testing webhooks #4671
Comments
FYI I'm also going to use this issue for testing webhook stuff - hope you don't mind! :D |
@Beamanator Absolutely no way! Make you own issue 😡 This is mine! Of course, feel free haha :) |
1 similar comment
✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release. |
✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release. (2) |
@isagoico Tested the linked issue by investigating other App PRs merged after this being deployed to production and it works 🎉 For more context, please see a following comment: https://github.com/Expensify/Web-Expensify/pull/31753#issuecomment-909132363 |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Action Performed:
Break down in numbered steps
Test if this issue gets auto close upon App PR being merged. For context: https://github.com/Expensify/Expensify/issues/173928
Expected Result:
Describe what you think should've happened
Actual Result:
Describe what actually happened
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platform:
Where is this issue occurring?
Version Number:
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Expensify/Expensify Issue URL:
View all open jobs on Upwork
The text was updated successfully, but these errors were encountered: