-
Notifications
You must be signed in to change notification settings - Fork 26
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
Make tests work with environment secrets. #91
base: 3.x
Are you sure you want to change the base?
Conversation
* Extending Invoice Client and Result classes * Health and Invoice Tests * Removed isPaid * Move requiresRefundEmail to bottom with default value
* LightningStore Client Test Suite * Renames getInvoice to getLightningInvoice * Adds amount, maxFeePercent and maxFeeFlat to payLightningInvoice
* Miscellaneous Client Test Suite * InvoiceCheckoutHtml Result Class + Test
* Notification Tests
Seems PRs from forked repos have no secrets available for security reasons (see https://github.blog/2020-08-03-github-actions-improvements-for-fork-and-pull-request-workflows/) . There seems to be a pull_request_target event that triggers then the workflow on the current master branch and not on the forked code as far as I understand. Defeats a bit the purpose so we might need another solution |
I would suggest we just remove phpunit test from github actions, and maybe make a policy that all PRs need to include a screenshot of passing tests? |
While repository secrets work on my own fork of this repo it seems that they don't for non-admin users on pull requests as they could leak confidential data on running the workflows. Also in every case $_ENV is empty because of PHP config,
getenv()
works though.