Automate Website Update on Processing Release with GitHub Workflows
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 35/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 停滞
- 技术栈
- github-actions, javascript
调研方向
从 scripts/fetchReleases.js、content/download/releases 和 .github/workflows/deploy.yml 开始，了解当前获取 release 和部署的流程。检查链接的 Processing4 issue 和 dispatch-event 参考，然后验证新的 Processing release 会触发 release 数据更新以及网站部署。
由索引模型根据 Issue 内容生成。
描述
Problem Statement
The Processing download page does not currently update automatically when a new version is released. As a result, the website must be updated manually through a multi-step process, which can be time-consuming for maintainers.
Proposed Solution
Instead of manually triggering fetchReleases.js, the update of the website can be automated with GitHub workflows whenever a new version of Processing is released. The automation process will fetch the releases from both the Processing and Processing4 repositories and write them to JSON files in the content/download/releases directory. For more information, refer to fetchReleases.js.
The action should make a new release for the website and deploy it by interacting with the existing deploy workflow.
Note: this change will require the Processing4 repository to dispatch an event upon the creation of a new release.
Benefits
- The website will always be up-to-date, providing users with accurate information about the latest version of Processing.
- The manual process of updating the website will be automated, reducing the workload on maintainers and improving efficiency.
- A better user experience, as users will have access to the latest information about Processing at all times.
References
Dispatch event: https://github.com/orgs/community/discussions/26323#discussioncomment-3251448
Notes
The corresponding issue on the processing4 repository can be found at https://github.com/processing/processing4/issues/665
- 主要语言
- MDX
- 星标
- 90
- 派生
- 122
- 平均合并
- 1 小时 43 分钟
- 30 天内合并 PR
- 3
贡献指南
这个仓库没有索引到贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
processing/processing-website 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 76/100
processing/processing-website#716 ·
-
难度 2/5 1-3 小时 新手友好度 68/100
processing/processing-website#703 ·
-
Good First Issue Help Wanted Reference
难度 1/5 1 小时以内 新手友好度 90/100
processing/processing-website#698 · 5 条评论 · 1 个 reaction ·
-
难度 1/5 1 小时以内 新手友好度 72/100
processing/processing-website#681 · 2 条评论 ·
-
难度 2/5 1-3 小时 新手友好度 65/100
processing/processing-website#646 · 3 条评论 ·
查看 processing/processing-website 的全部 Issue
相似的 Issue
-
难度 1/5 1 小时以内 新手友好度 92/100
vicharanashala/fln#564 ·
-
难度 2/5 1-3 小时 新手友好度 78/100
haskell-actions/setup#152 ·
-
feature-request helm
难度 2/5 1-3 小时 新手友好度 68/100
gravitational/teleport#69785 ·
-
A cancelled tests run makes the coverage comment workflow fail and reports it as a red check on main 未关闭area: ci bug perceived difficulty: 3
难度 2/5 1-3 小时 新手友好度 78/100
Nitjsefnie-Harness-Commons/daedalus#921 · 1 条评论 ·
-
难度 2/5 1-3 小时 新手友好度 86/100
TencentCloud/Octop#1007 ·