Split the meeting scraper into two parts - one for the past meetings and one for the next meeting (which has a different format from the past meetings).
Checklist
All checks are run in GitHub Actions. You'll be able to see the results of the checks at the bottom of the pull request page after it's been opened, and you can click on any of the specific checks listed to see the output of each step and debug failures.
[x] Tests are implemented
[x] All tests are passing
[x] Style checks run (see documentation for more details)
[x] Style checks are passing
[x] Code comments from template removed
Questions
Due to the two different formats of meetings (past v. next), I had to create separate _parse methods for the next meeting. Let me know if this is unwanted
Summary
Issue: #681
Split the meeting scraper into two parts - one for the past meetings and one for the next meeting (which has a different format from the past meetings).
Checklist
All checks are run in GitHub Actions. You'll be able to see the results of the checks at the bottom of the pull request page after it's been opened, and you can click on any of the specific checks listed to see the output of each step and debug failures.
Questions
Due to the two different formats of meetings (past v. next), I had to create separate
_parsemethods for the next meeting. Let me know if this is unwanted