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
{{ message }}
Repository navigation
[$500] [HOLD for payment 2023-12-06] Local testing of GitHub Actions #13604
There is no easy way to locally test our GitHub Actions.
Why this is important
When we make changes to GitHub Actions, it's difficult to generate confidence that a PR will work and do what it is intended. This creates headaches:
It's harder to review GitHub Actions PRs and they need to be reviewed more carefully
We need to live-test things which is often disruptive
The best approximation is testing using another repo. We often use https://github.com/Andrew-Test-Org/Public-Test-Repo), but still the workflows you're testing there are not the same as the one's you're testing in E/App, and there may be different constraints in place, etc...
There's a slower feedback loop with simple mistakes in Actions and Workflows, leading to development taking longer
BugZero Checklist: The PR adding this new feature has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
[@sobitneupane] Please propose regression test steps to ensure the new feature will work correctly on production in further releases.
[] Link the GH issue for creating/updating the regression test once above steps have been agreed upon.
Activity
radoslawkrzemien commentedon Jan 26, 2023
I'd like to have a look at this
[-][HOLD] Local testing of GitHub Actions[/-][+]Local testing of GitHub Actions[/+]306 remaining items
melvin-bot commentedon Nov 29, 2023
BugZero Checklist: The PR adding this new feature has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
dangrous commentedon Dec 8, 2023
@sobitneupane we need to get a BZ in here to handle your payment, right?
sobitneupane commentedon Dec 8, 2023
Yes, @dangrous. There were two PRs in this issue. One of them was reviewed by me and the other by @rushatgabhane
melvin-bot commentedon Dec 8, 2023
Triggered auto assignment to @muttmuure (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.melvin-bot commentedon Dec 8, 2023
Bug0 Triage Checklist (Main S/O)
Platformsin OP are ✅)dangrous commentedon Dec 8, 2023
@muttmuure not a bug, but we're ready for payment for two C+ reviews:
Thank you!
muttmuure commentedon Dec 13, 2023
@sobitneupane - $500
@rushatgabhane - $500
melvin-bot commentedon Dec 13, 2023
Job added to Upwork: https://www.upwork.com/jobs/~016c26e8384c322e36
melvin-bot commentedon Dec 13, 2023
Triggered auto assignment to Contributor-plus team member for initial proposal review - @ArekChr (
External)muttmuure commentedon Dec 13, 2023
both should request payment in NewDot - the summary is above here
sobitneupane commentedon Dec 15, 2023
#13604 (comment)
Requested payment on newDot.
JmillsExpensify commentedon Dec 15, 2023
$500 payment approved for @sobitneupane based on this comment.
JmillsExpensify commentedon Dec 26, 2023
$500 payment approved for @rushatgabhane based on comment above.