QuantEcon / QuantEcon/actions

Instant placeholder PR comment + shared preview comment-script extraction (PLAN item 6)

Open
#153 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Shell
Stars
0
Forks
1
Avg merge
32m
Merged PRs (30d)
3

Description

#92 Phase 2: instant first signal on preview PRs, plus the shared comment-script extraction (PLAN item 6).

  • Instant placeholder PR comment — no container, no checkout (REST changed-files) — with deterministic pr-N links; today both actions comment only after a successful deploy (preview-netlify/action.yml:101, preview-cloudflare/action.yml:148)
  • Extract the shared comment script: the two github-script bodies (preview-netlify/action.yml:111-186 vs preview-cloudflare/action.yml:159-242) now differ by ~12 lines (a deploymentUrl const, two title lines, two marker lines, a 7-line "This deployment" block) against PLAN item 6's recorded "only 2 lines differ"

The Cloudflare stable-alias half of the original bundle shipped in v0.11.1 (#131). The extraction also serves the Workers path in #145, whose change-detection and comment machinery is identical; the placeholder comment should emit the Workers alias URL template once QuantEcon/infrastructure#4 lands.

Contributor guide

Open the contributing guide

First steps

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

Research direction

Start by comparing preview-netlify/action.yml:101-186 with preview-cloudflare/action.yml:148-242 and review the REST changed-files requirement. Trace how both actions currently post comments after deployment, then verify that the placeholder comment, deterministic pr-N links, and shared comment script cover the stated Netlify, Cloudflare, and Workers paths.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, shell
Domain
ci-cd, devops
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.