今日已更新 374 条资讯 | 累计 23957 条内容
关于我们

开源项目

GitHub热门开源项目精选

1372
篇文章

共 1372 篇 · 第 27/69 页

GitHub Blog

Transitioning as a hubber

How GitHub's culture and benefits helped me be the best version of myself. The post Transitioning as a hubber appeared first on The GitHub Blog .

Natalie Guevara 2026-06-26 20:00 👁 8 查看原文 →
Dev.to

Docs as Code: Build a CI/CD Pipeline for Your Documentation

Your code has CI/CD. Your docs don't. Every modern engineering team has automated builds, tests, and deployments for their code. But documentation? That's still someone manually exporting a PDF, uploading it to Confluence, and hoping it's the latest version. This post shows you how to treat documentation like code: version-controlled Markdown in a Git repo, automatically rendered to branded PDFs on every push. No manual steps, no stale documents. The stack PaperQuire gives you three tools that work together: .paperquire.yml — project config that locks in your template, branding, and document options CLI — paperquire render and paperquire batch for scripting and local builds GitHub Action — paperquire/render-action for automated builds in CI Each one builds on the previous. The config file means no one has to remember flags. The CLI means you can test locally. The action means it happens automatically. Step 1: Add a project config Drop a .paperquire.yml in your repo root. Every render — GUI, CLI, and CI — picks up these settings automatically: template : corporate toc : true toc-depth : 3 h1-page-break : true cover : title : " Project Documentation" author : " Engineering Team" branding : primary-color : " #2563eb" This is your single source of truth for how documents look. Change it once, and every PDF across every environment updates. Step 2: Test locally with the CLI Before committing, verify your docs render correctly: # Render a single file paperquire docs/architecture.md -o out/architecture.pdf # Batch render the entire docs directory paperquire batch ./docs -o ./out # Dry run — validate without producing output paperquire batch ./docs --dry-run The CLI reads .paperquire.yml automatically. The output is identical to what CI will produce. Step 3: Automate with the GitHub Action Add one workflow file and your docs build themselves: # .github/workflows/docs.yml name : Build Documentation on : push : paths : - ' docs/**/*.md' - ' .paperquire.yml' jobs : render : ru

paperquire 2026-06-26 05:37 👁 7 查看原文 →
The Verge AI

Slate’s electric truck: all the news about the ultra-minimal EV

Slate Auto is a new startup that emerged out of a secretive project called “Re:Car” within Re:Build Manufacturing, a domestic manufacturing project backed by Amazon founder Jeff Bezos. The company’s first electric vehicle is a barebones electric pickup that’s roughly a third of the size of your typical gas-powered truck. And the proposal is pretty […]

Andrew J. Hawkins 2026-06-25 23:59 👁 8 查看原文 →
← 上一页 25 26 27 28 29 下一页 →