Add GitHub workflow, cron-based to update driverless (AirPrint, IPP Everywhere) printer list
評估
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 新手友好度
- 68/100
研究方向
從 driverless/update-printer-list.sh 及其產生的檔案 public/assets/json/driverless.json 開始;檢查該腳本如何使用 curl 和 Python,包括 sys 和 json。接著檢視 CUPS Snap repo 中的更新與版本控制工作流程,以及 GitHub create-pull-request action。當一個 cron workflow 執行該腳本,並為更新後的印表機資料開啟 pull request 時,即表示完成。
由索引模型根據 Issue 內容生成。
描述
See issue #223, starting with this comment to the end.
@michaelrsweet said:
The current scripts merge the AirPrint and IPP Everywhere lists. Mopria does not provide a public list of printers (unfortunately), but the number of Mopria-ready printers that are not AirPrint or IPP Everywhere is probably close to (if not) 0.
I ran my scripts manually this time. I normally have them setup to run on one of my development systems once a month since the lists don't change that often. I don't think we could do this via GitHub CI directly - maybe we could create a PR but I'm not sure. The scripts can certainly be run from CI, it is just how to generate the PR with the changes? (I know I probably don't have the time to make that work right now, maybe later...)
... and to follow up on this, apparently there is a GitHub action for this. So it is possible we can do it fairly easily, but again I don't have time to write it up today...
From a clone of the repository:
cd driverless ./update-printer-list.shThe updated "public/assets/json/driverless.json" file is then ready to be committed and/or turned into a PR.
The script uses curl and python, with the python sys and json modules/libraries (in case they are not in the default CI running image...)
For generating PRs also have a look at the workflows for update and versioning automation in the CUPS Snap repo.
@rudra-iitm @gativarshney @rkt0209 could somebody of you have a look?
- 主要語言
- TypeScript
- 星號
- 20
- 分支
- 43
- 平均合併
- 7 小時 45 分鐘
- 30 天內合併 PR
- 8
環境準備
在瀏覽器裡用你自己的 GitHub 帳號啟動這個專案的開發容器。
- 沒有 Dockerfile 或 Docker Compose 檔案
- 沒有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
OpenPrinting/openprinting.github.io 的其他 Issue
-
難度 4/5 3-5 天 新手友好度 35/100
OpenPrinting/openprinting.github.io#240 · 3 則留言 ·
-
難度 3/5 1-2 天 新手友好度 45/100
OpenPrinting/openprinting.github.io#164 · 1 則留言 ·
-
難度 5/5 一週以上 新手友好度 35/100
OpenPrinting/openprinting.github.io#159 · 7 則留言 ·
查看 OpenPrinting/openprinting.github.io 的全部 Issue
相似的 Issue
-
bug
難度 2/5 1-3 小時 新手友好度 76/100
-
bug
難度 2/5 1-3 小時 新手友好度 62/100
AloisSeckar/elrh-cosca#36 ·
-
難度 2/5 1-3 小時 新手友好度 73/100
cursor/community-plugins#572 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 72/100
MUKE-coder/grit#228 ·
-
bug status:needs-triage
難度 2/5 1-3 小時 新手友好度 74/100
dongdongbh/Mindwtr#1587 ·
維護者通常 1 天內回覆