A support teammate wants to know what a PR changed for a customer. The diff is the right evidence, but asking them to read every file is a poor handoff. Keep the request beside the change so someone reviewing the video can find the original discussion.
Connect the repository and the account that will pay
Install the ngram GitHub App on the repository. The installer follows the redirect to link their ngram account and authorize uploads. An organization owner may need to approve installation. People with write access can then request videos. Check the linked account’s balance before starting. An account without a paid subscription produces videos with an ngram watermark and end card.
Choose a pull request, issue or release
On a PR, add a new comment such as “@ngram-ai explain the new export options to customer support in 20 seconds.” The app can use the PR description, changed code and relevant comments. On an issue, ask “@ngram-ai explain the reported upload problem to our triage team in 15 seconds.” Frame an unresolved problem as a report. The issue does not establish that a fix shipped.
For a release, put “@ngram-ai explain this release to existing customers, focus on the new export option” in the release notes before publishing. The publication event starts the request. Editing notes after publication or editing an old comment will not start a new video.
Find and check the result
The GitHub walkthrough shows the acknowledgment and finished PR reply, followed by a release-note example. For a release, look at the end of the notes and in its attached files. For a PR or issue, return to the bot’s reply. If the inline upload could not complete, follow the video link in the reply.
Watch the explanation alongside the original thread. Does it show an action the intended viewer can take? Does it describe an unmerged proposal as available? Use Open in ngram to revise a result that needs work. For broader announcements, the changelog video guide covers choosing which changes to explain.
When the request gets no reply
Check that the app is installed on this repository, the installer finished linking an account and the requester has write access. Verify that you made a new mention rather than editing one. If the app responded but could not finish, follow the reason in its reply before retrying. Keep routine maintenance and non-customer-facing changes in writing. For a change with a visible outcome, the product update workflow can help you choose the audience.
