[FEATURE] Add release binaries using a workflow

Open
#249 0 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
52/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
github-actions, go
Domain
ci-cd, release

Research direction

Start by reviewing the referenced .github/workflows/release.yaml in the linked fork and compare it with this repository's existing workflow setup. Adapt the release workflow for this Go project, then verify that future releases publish usable pre-built binaries for installation and aqua registration.

Written by the indexing model from the issue text.

Description

enhancement
Describe the feature

For future versions, it would be useful to make available pre-built binaries for this tool.

Motivation

While installing with go is fairly practical, some workflows benefit from quickly installing pre-built binaries. I, for example, use mise en place to install dev dependencies across environments.
Making binaries available would also enable this package to be included in the aqua registry.

I added a release file to my personal fork of the project to enable this workflow I just mentioned. It would be nice to see the same option upstream.

https://github.com/TheGB0077/pg-schema-diff/blob/main/.github/workflows/release.yaml

Dominant language
Go
Stars
884
Forks
82
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from stripe/pg-schema-diff

All issues in stripe/pg-schema-diff

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.