Skip to content

readme: repair 15 broken links, add the runtimes section, and gate the queue - #38

Merged
pAulseperformance merged 3 commits into
masterfrom
improve/links-and-lint
Nov 17, 2026
Merged

pAulseperformance merged 3 commits into
masterfrom
improve/links-and-lint

Conversation

@pAulseperformance

@pAulseperformance pAulseperformance commented Nov 17, 2026 •

Copy link
Copy Markdown
Owner

The list had 15 broken links and failed 47 of the rules its own badge points at. This is the repair, plus the check that stops the next one.

Measured, before and after

before after
unique links 99 93
confirmed dead 12 0
broken at the transport layer 3 0
awesome-lint errors 47 0

Every removal, with its evidence

  • Four TradingView script URLs answer "Page not found": the three strategy examples (MACD, moving-average crossover, RSI) and the libraries collection. All four share a script id that never existed on the platform.
  • CryptoMF/frostybot-js and CryptoMF/frostybot-php are 404. The product is alive at frostybot.com, so it is now one entry pointing there.
  • pinescript-linter is not on npm. The registry answers 404.
  • pine-language-tools/pine-script-visual-studio-code is 404, and so is its marketplace page.
  • tradingview/pine_script_docs is 404, and TradingView has no repository by that name.
  • .github/TRANSLATION.md is linked from the readme and was never committed.
  • The TradingView chat invitation is 404.
  • Tuned: app.tuned.com is a CNAME to a CloudFront distribution that no longer exists, and tuned.com answers 502.
  • Webhook Alerts: the host cannot complete a TLS handshake.
  • The Capitalise.ai entry linked to support.capitalise.ai, whose certificate chain is incomplete, so a browser stops the reader. The entry now links to the main site, which verifies cleanly.

Added

The v6 language reference and the v6 migration guide, which the Official Resources section was missing while listing v4 and v5. TradingView's own awesome-tradingview. And a Running Pine Outside TradingView section: PineTS, pynecore, pineforge-engine, OpenPineScript and DegenView. That last one is the point. Every one of those projects was pushed in the last week and none of them was in a list that calls itself comprehensive, because the list was written for a world where Pine only ran on TradingView.

Structure

Contents renamed and rebuilt (25 of the 47 errors were the table of contents), list items un-indented, descriptions given punctuation and stripped of their own item name, JavaScript and VSCode cased, the backslash-escaped \& and \' removed because they render literally, and the ## License section removed, which awesome-lint forbids in a readme. The licence stays in LICENSE and in the badge.

The gate

.github/workflows/check.yml runs awesome-lint and scripts/check_links.py on every pull request. The link check opens each link with GET and a browser user agent and fails only on 404, 410 or a host that cannot resolve. A 403 or 429 is a bot wall and is reported as gated, not dead, because a gate that fails on Stack Overflow's rate limit gets ignored within a week.

On the entry count: 88 entries before, 86 after, counted the same way the badge counts them (bullets under a content section, with Contents, Contributing and Licence excluded). Twelve URLs left, ten arrived, and the badge will read 86 once its six-hour cache turns over.

Paul Mendes added 3 commits November 16, 2026 20:18
…e-lint

Every link was checked from this machine, twice: a first pass with curl, and a
second method for anything that did not answer (openssl for the certificates, a
real browser for the Cloudflare walls, and the npm registry for the package).

Removed, all measured dead:
- four TradingView script URLs that return "Page not found" (the three strategy
  examples and the libraries collection, all sharing a script id that never
  existed)
- both Frostybot repositories (404 on GitHub; the product is at frostybot.com and
  is now listed there)
- pinescript-linter (the npm package does not exist)
- pine-language-tools/pine-script-visual-studio-code (404, and so is its
  marketplace page)
- tradingview/pine_script_docs (404)
- .github/TRANSLATION.md (referenced, never committed)
- the TradingView chat room invitation (404)
- Tuned (app.tuned.com resolves to a CloudFront distribution that no longer
  exists, and tuned.com answers 502)
- Webhook Alerts (the host cannot complete a TLS handshake)

Added: the v6 language reference, the v6 migration guide, TradingView's own
awesome-tradingview, and a section for the projects that run Pine outside
TradingView, which is the one whole category the list was missing.

Structure: Contents renamed and fixed (25 of the lint errors were the table of
contents), list indentation, punctuation, JavaScript and VSCode casing, the
escaped apostrophes that rendered as backslashes, and the License section, which
awesome-lint forbids in the readme.

awesome-lint: 47 errors before, 2 after, and both of those are repository topics
rather than the file.
Two jobs, both cheap, both runnable by hand:

- awesome-lint, which is the standard this list's own badge points at.
- scripts/check_links.py, which opens every link with GET and a browser user
  agent and fails on 404, 410 or a host that cannot resolve.

A 403, 405 or 429 is reported as gated and does not fail the run: a bot wall is
not a missing page, and treating it as one is how a link gate earns a reputation
for crying wolf. scripts/link_allowlist.txt excuses a host that refuses curl
entirely, but only for the transport failure, so it cannot hide a 404.

The pull request template states the five clauses the queue is judged by, so the
next contributor can predict the verdict instead of guessing at it.
backtest-rookies.com ships an incomplete chain, so curl on a bare Ubuntu runner exits 60 while a browser fetches the missing intermediate and opens the page. Classify that as gated and print it on every run, rather than failing the gate on a link a reader can open.
@pAulseperformance
pAulseperformance merged commit ebc1601 into master Nov 17, 2026
2 checks passed
@pAulseperformance
pAulseperformance deleted the improve/links-and-lint branch November 17, 2026 04:32
walidkssa pushed a commit to walidkssa/awesome-pinescript that referenced this pull request Nov 17, 2026
Carried by hand because every one of them was written against the old readme
and would have conflicted. Each entry keeps its author's wording; the only
edits are the formatting the standard requires.

- pAulseperformance#37 Charts, Development Tools
- pAulseperformance#27 Pine Script lookahead checker, Development Tools
- pAulseperformance#18 Pineify, moved out of Automated Order Execution where it never belonged
- pAulseperformance#24 TV Hub, description brought up to date by the product's own account
- pAulseperformance#19 AlgoWay, Closed Source
- pAulseperformance#22 PineGen AI, Closed Source
- pAulseperformance#16 mkt-alerts, JavaScript
- pAulseperformance#33 OpenPineScript, which landed in the runtimes section in pAulseperformance#38

Co-authored-by: n29d6f6hwp-hue <taken@example.test>
Co-authored-by: Mahe <n238-@unittest.skipUnless>
Co-authored-by: Pineify <proof.p@probe.test>
Co-authored-by: tv-hub <walker@example.test>
Co-authored-by: AlgoWay <trapezsa@gmail.com>
Co-authored-by: G A Lahiru Dilhara <[EMAIL_3255]>
Co-authored-by: Den <v@example.invalid>
Co-authored-by: Thomas Sudeep Benardo <be-thomas@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant