Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Add a post-deploy smoke workflow to loop-audit

未关闭
#31 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
56/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
github-actions, typescript
领域
ci-cd

调研方向

Start with the course workflow in loop-audit and the referenced parent issue #15; the payload does not name a workflow file or smoke test, so locate those in the repository. Check the workflow with actionlint and record the failing run in the PR description. Done when the reference lists stop-ship triggers, the deploy URL is declared as a job output and passed to the smoke job, actionlint passes, and action versions match current docs.

由索引模型根据 Issue 内容生成。

描述

ready-for-agent

Parent

#15

What to build

A repo owner can copy a post-deploy smoke workflow from loop-audit that catches a bad deploy and rolls it back by rule. The stop-ship triggers are written before the deploy. The smoke job receives the deploy URL, so the smoke test runs against the deployment and not against an empty base URL.

Acceptance criteria

  • actionlint on the course's workflow, as written, reports the reference to an undeclared job output. The PR description records the run.
  • After the deploy job declares the URL as a job-level output, actionlint passes.
  • The reference sits in loop-audit and lists the stop-ship triggers.
  • Action versions in the workflow match current docs.
主要语言
TypeScript
星标
0
派生
0
平均合并
3 小时 33 分钟
30 天内合并 PR
13

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

gregogun/gstack 的其他 Issue

查看 gregogun/gstack 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。