Support setting a post hook
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 45/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 停滞
- 技术栈
- github-actions, javascript, node.js, typescript
调研方向
Start by tracing the existing github-script action entry point and how it handles the script input, then compare the node20 post-hook model and core.saveState behavior described in the issue. Done means a new post input runs cleanup after the job while preserving existing usage and supporting shared state.
由索引模型根据 Issue 内容生成。
描述
Is your feature request related to a problem? Please describe.
With actions/github script it's not possible to setup some cleanup logic to run at the end of the job.
Describe the solution you'd like
A post hook is supported by node20 actions. Adding support for this would not be too difficult on github-script, as it's just a separate function that can be set on an additional post input.
The change would be fully backwards compatible and not too disruptive.
Usage would look like this:
- name: My github script
uses: actions/github-script@v7
with:
script: |
console.log("Running my github script");
post: |
console.log("Running cleanup logic for my github script");
State sharing between both scripts would be supported out of the box by core.saveState, so this would be a very powerful addition.
I'm willing to work on a PR for this feature in the next few days.
Describe alternatives you've considered
- Using an additional action with
if: always()for cleanup, this requires putting the cleanup step at the end of the job, potentially far from the step it's cleaning after. - Using a node action directly: this would require duplicating parts of this project for toolkit set up.
Additional context
Use case where the need for this has come up: creating a "check" (github.rest.checks.create) at the beginning of a job, and making sure the check is marked as completed at the end (either with success or failure based on the job status)
- 主要语言
- TypeScript
- 星标
- 5k
- 派生
- 586
- PR 合并指标
- 30 天内没有已合并 PR
贡献指南
这个仓库没有索引到贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
actions/github-script 的其他 Issue
-
难度 3/5 1-2 天 新手友好度 48/100
actions/github-script#728 ·
-
难度 3/5 1-2 天 新手友好度 52/100
actions/github-script#727 · 1 个 reaction ·
-
{ 未关闭
难度 5/5 一周以上 新手友好度 10/100
actions/github-script#724 ·
-
难度 3/5 1-2 天 新手友好度 55/100
actions/github-script#723 · 1 条评论 ·
-
难度 3/5 1-2 天 新手友好度 55/100
actions/github-script#714 · 1 条评论 · 4 个 reaction ·
查看 actions/github-script 的全部 Issue
相似的 Issue
-
blocklist removal
难度 2/5 1-3 小时 新手友好度 65/100
MetaMask/eth-phishing-detect#296544 ·
-
难度 2/5 1-3 小时 新手友好度 70/100
pastelsky/bundlephobia#1122 ·
-
难度 2/5 1-3 小时 新手友好度 70/100
-
category/development priority/P2 scope/file-operations scope/testing type/enhancement
难度 2/5 1-3 小时 新手友好度 75/100
-
难度 2/5 1-3 小时 新手友好度 75/100