Fix dot submissions: restore auth, add public feedback, auto-populate from inbox - #9
Merged
devyanijain merged 4 commits intoAug 31, 2026
Conversation
GitHub secret scanning replaced the token value with '******' but did
not close the backtick template literal, causing a JS syntax error that
silently swallowed the entire headers object and made all feedback
submissions fail.
Restore the correct header: `token ${_tk}`
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>The public 'what was it like working with Devyani' field (pub.t) was never written to the inbox issue. Add a '💬 Public feedback' section so all feedback is captured in one place. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 02919104-34f1-44e8-91db-7bfd688b1b6e
Mark the first teal/red/purple dots as submitted with data from the golden-seeds-inbox issues so they appear as planted on page load. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 02919104-34f1-44e8-91db-7bfd688b1b6e
Instead of hardcoding submitted dots, fetch the golden-seeds-inbox issues on every page load and hydrate the dot field in-place. This means any new submission automatically appears for all visitors without needing a code change. - submittedDots starts empty; loadSubmittedDots() fills it async - Dots render immediately (blank), then light up after the fetch - Issues are assigned to dots in creation order, per color/relationship - Anonymous and [Test] issues are skipped Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 02919104-34f1-44e8-91db-7bfd688b1b6e
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
What broke
GitHub secret scanning replaced the
Authorizationheader value with******but didn't close the backtick template literal — causing a JS syntax error that silently made every submission fail to post.What's fixed
🔧 Bug fixes
Authorizationheader inpostPrivateFeedback— submissions now actually post to the inboxpub.t) to the GitHub issue body so the "what was it like" field is captured going forward✨ New: auto-populate submitted dots for all visitors
Instead of dots only appearing for the person who submitted them (in-memory only), the page now fetches
golden-seeds-inboxissues on every page load and hydrates the dot field dynamically:[Test]issues are skippedPreviously submitted dots
All 3 real submissions (Rachel Florence, Ricky Zhang, April) are preserved — they live in the GitHub Issues inbox and will be fetched and shown dynamically.