Add ALESCo meeting minutes for July 30, 2026 - #828
Merged
Conversation
ramereth
approved these changes
Aug 11, 2026
jonathanspw
reviewed
Aug 11, 2026
jonathanspw
reviewed
Aug 11, 2026
jonathanspw
requested changes
Aug 11, 2026
andrewlukoshko
force-pushed
the
alesco-meeting-minutes-2026-07-30
branch
from
August 11, 2026 14:54
82f039b to
28c2a57
Compare
Conan-Kudo
approved these changes
Aug 11, 2026
andrewlukoshko
force-pushed
the
alesco-meeting-minutes-2026-07-30
branch
from
August 11, 2026 15:14
28c2a57 to
ef16643
Compare
jonathanspw
approved these changes
Aug 11, 2026
bathomas
approved these changes
Aug 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds meeting minutes for the ALESCo meeting held on 2026-07-30, and links the page from the meeting minutes index.
Note: #823 adds the July 02 and July 16 minutes and touches the same index list, so one of the two PRs will need a trivial rebase after the other merges.