Discord GitHub Notifications fails for every new stargazer

Open

#2,255 opened on Sep 13, 2026 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 3/5
Estimated time: 1-2 days
Newbie friendliness: 58/100

Issue type: Bug
Clarity: Mostly clear
Activity status: Active
Tech stack: github-actions
Domain: ci-cd, devops

Research direction

Start with the notify-discord job and the “Send to Google Apps Script (Stars only)” step in the Discord GitHub Notifications workflow, then inspect run #43300 and the linked neighboring runs. Verify the endpoint failure and determine whether the workflow should be repaired or let the Discord notification continue when tracking fails. Done means new-stargazer runs complete without skipping Discord notification.

Written by the indexing model from the issue text.

Description

⚙️ In-progress 🐞 Bug 📌 Root caused

Summary

The Discord GitHub Notifications workflow is currently failing for new stargazers. I noticed this when starring the repository, and the runs immediately before and after mine failed in the same way for other users.

Evidence

Run #43299 (wunala-bot): https://github.com/unclecode/crawl4ai/actions/runs/34734529387
Run #43300 (Beverly621): https://github.com/unclecode/crawl4ai/actions/runs/34734586165
Run #43301 (haoyun18881-beep): https://github.com/unclecode/crawl4ai/actions/runs/34734744872

In run #43300, the notify-discord job fails at:

Send to Google Apps Script (Stars only)

The check annotation reports:

Process completed with exit code 22.

The workflow uses curl -fSs to POST to secrets.GOOGLE_SCRIPT_ENDPOINT, so exit code 22 indicates that the endpoint returned an HTTP error response. Because this first step fails, Set webhook based on event type and Discord Notification are skipped.

Expected behavior

A temporary failure in the optional stargazer-tracking endpoint should ideally not fail the complete workflow or prevent the Discord notification from running.

Possible resolution

There appear to be two possible directions:

Fix or redeploy GOOGLE_SCRIPT_ENDPOINT if the current failure is only a service/configuration problem.
If spreadsheet tracking is intended to be best-effort, handle this step as a warning (for example with continue-on-error: true) so the Discord notification can still run.

Would the maintainers prefer the second behavior? If so, I would be happy to submit a focused PR targeting develop.

Dominant language: Python
Stars: 83.9k
Forks: 8.7k
Avg merge: 3d 7h
Merged PRs (30d): 11

Contributor guide

Open the contributing guide

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

Schema regression: derivation conversion_failure reverted Open

Difficulty 1/5 Under an hour Newbie friendliness 90/100

elong0527/yamaa#708 · Opened Sep 21, 2026
RadioSelectButtonGroup does not render as a button group through bootstrap_field Open

bug

Difficulty 2/5 1-3 hours Newbie friendliness 86/100

zostera/django-bootstrap4#894 · Opened Sep 21, 2026
[Bug]: control_ui.show_thinking = false does not stop the live reasoning stream, so thinking events and done.reasoning_content still reach the web UI Open

Difficulty 2/5 1-3 hours Newbie friendliness 78/100

use-agent-os/agent-os#3276 · Opened Sep 21, 2026
Build fails with LTO enabled: conflicting types for z_shared_sw_isr_table between isr_tables.c and sw_isr_table.h Open

Difficulty 2/5 1-3 hours Newbie friendliness 88/100

zephyrproject-rtos/zephyr#119726 · Opened Sep 21, 2026
[Bug]: redact_sensitive_text does not recognise Discord bot tokens Open

area/auth bug comp/agent P3 platform/discord type/security

Difficulty 2/5 1-3 hours Newbie friendliness 88/100

NousResearch/hermes-agent#117848 · Opened Sep 21, 2026

More Python issues