With cogent3workshop as a forkable repo that they will be potentially using as their environment for working with cogent3, attendees could raise a pull request containing some code they have questions about that we can review and provide comments without merging into the main branch.
I don't think this is the right mechanism. We want to reinforce their usage of standard GitHub repo tools for raising issues and the process for doing that:
how to make a minimal algorithm and minimal data
raising a topic on GitHub discussions, embedding code using the syntax gates, or as an attachment OR raising a GitHub issue if it's a bug or feature request
With cogent3workshop as a forkable repo that they will be potentially using as their environment for working with cogent3, attendees could raise a pull request containing some code they have questions about that we can review and provide comments without merging into the main branch.