Menu

Replace email attachments in CI — upload a ZIP from GitHub Actions and get a shareable link
📰

Replace email attachments in CI — upload a ZIP from GitHub Actions and get a shareable link

DEV Community: github·TiniDrop·8 days ago
#AKqFXOq2
#devtogithub#technology#devto#dev#upload
Reading 0:00
15s threshold

Your CI already builds the artifact.

Then someone pastes it into Slack as a 40 MB attachment — or opens a throwaway Google Drive link that expires next week with no signal that anyone opened it.

If the person on the other end is not living in GitHub Releases, you need a handoff link : one URL, browser-readable, optional password/expiry, and a simple “was it opened?” check.

This post walks through a practical pattern:

Build a ZIP (or PDF) in GitHub Actions

Upload it with one authenticated curl

Post the share URL back on the PR (or into Slack)

I use TiniDrop for the share step because that is what we built for this exact loop — but the workflow shape is the same idea wherever you land the file: artifact in CI → link out → humans click a URL, not a binary.

When this beats GitHub Releases (and email)

Use a share link when:

The recipient is a client, investor, or teammate who is not cloning repos

You are shipping a finished ZIP / PDF / HTML preview , not ongoing source

You want a lightweight “did they…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.