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
Alongside the config generation PR (#502) we need to implement the following:
When there is a merge to master:
Run utils/scan_electrums.py which will identify current working / failed electrums.
Run utils/generate_app_configs.py which will output json files for each app (web, mobile, desktop). It will reference the electrums_scan_report.json to exclude any entries which are failing.
Push the generated app config json files to master branch, so they are available for apps to grab during build. Also push the electrum_scan_report .json file to master - we can use this to inform electrum maintainers if their servers need attention.
Create exclusion in the CI flow so that updating the json files in master does not trigger the CI workflow, so we can avoid an infinite loop which melts down githubs servers.
Once a day:
Run utils/scan_electrums.py which will identify current working / failed electrums.
Push the electrum_scan_report .json file to master - we can use this to inform electrum maintainers if their servers need attention.
The text was updated successfully, but these errors were encountered:
Alongside the config generation PR (#502) we need to implement the following:
When there is a merge to master:
utils/scan_electrums.py
which will identify current working / failed electrums.utils/generate_app_configs.py
which will output json files for each app (web, mobile, desktop). It will reference the electrums_scan_report.json to exclude any entries which are failing.Once a day:
utils/scan_electrums.py
which will identify current working / failed electrums.The text was updated successfully, but these errors were encountered: