Closed github-actions[bot] closed 4 days ago
Name | Link |
---|---|
Latest commit | 7a31dab863e11fc39bdc3f1a5fc299f21f79e8d7 |
Latest deploy log | https://app.netlify.com/sites/ols-bebatut/deploys/66f9617f7f210d0008a4ce2e |
Deploy Preview | https://deploy-preview-893--ols-bebatut.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
@bebatut the update-schedule action doesn't trigger the schedule update for the DRA track - I can see in this PR some changes in Catalyst but not DRA. Can you let me know if I should create a separate PR for that?
@bebatut the update-schedule action doesn't trigger the schedule update for the DRA track - I can see in this PR some changes in Catalyst but not DRA. Can you let me know if I should create a separate PR for that?
The Python was raising an error when parsing the DRA spreadsheet and it was not making the bash script in error mode so you could not see the error. What is why the DRA schedule was not updated.
The error was in the Week
column: every row should have a value in the Week
column otherwise the script doesn't know which week it corresponds to.
Can you check the updates?
If there were changes in cohort call dates, we need to remove the entries corresponding to the calls on previous date from the schedule.yaml
Brilliant stuff! Thanks @bebatut - all sorted!
Automatic schedule update done via GitHub Action once a week