feat: Include latest "config.yaml" to each release zip file

Open Beginner friendly
  • Is something wrong?
#81 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
66/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
go, yaml
Domain
build-system, release

Research direction

The issue asks that the latest config.yaml be bundled into each release zip, but it does not name the release workflow or packaging file. Start by finding where release archives are built in the repository (its release or CI configuration) and check which config.yaml the CLI reads by default. Done means a release zip contains config.yaml at the expected path, and the change is verified by building a release archive locally or in CI.

Written by the indexing model from the issue text.

Description

enhancement
Problem

New people won't know you can configure this software using a file instead of argument. By addin config.yaml into the zip file they will know about it.

Proposed solution

Improve packaging to include config.yaml file

Alternatives considered

No response

Area

CLI

Contribution
  • I am willing to open a PR for this.
Dominant language
Go
Stars
1.5k
Forks
173
Avg merge
7d 5h
Merged PRs (30d)
4

Getting set up

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 karust/openserp

All issues in karust/openserp

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.