💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

Hello @fuhrmanator! Since your lab starts this Wednesday, I understand the urgency.

Looking closely at your console logs (TypeError: Cannot read properties of null (reading 'dataset')), this appears to be a frontend regression/bug on GitHub Classroom's side affecting how the form renders the repository visibility or the slug field. The "CSRF Token" error is likely a secondary failure because the broken JavaScript prevents the form from submitting correctly.

While waiting for GitHub staff to deploy a fix, you need a workaround to get your assignments ready. Please try these steps:

Bypass the Buggy UI (The Duplication Workaround): Instead of updating an existing assignment where the UI crashes, try creating a completely new assignment. Sometimes, the bug only triggers on the 'Edit/Update' page of older assignment templates.

Use the GitHub Classroom CLI:
If the web interface is completely broken, you can bypass the frontend entirely using the official GitHub Classroom command-line tool.

Install the CLI.

You can often clone, create, or manage assignments directly from your terminal, which bypasses these JavaScript/CSRF web errors.

Hard Reload & Different Browser:
Just to rule out any cached broken scripts, try a "Hard Reload" (Ctrl + F5 or Cmd + Shift + R) or attempt to edit the assignment using a completely different browser profile (e.g., Firefox if you are on Chrome) with zero extensions.

I hope one of these workarounds allows you to set up the cutoff date for your Wednesday lab! Please let us know if any of these methods successfully bypass the error.