8000 docs: build.go suggested edits for optional --release flag by barriebyron · Pull Request #1240 · ignite/cli · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

docs: build.go suggested edits for optional --release flag #1240

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Jun 15, 2021

Conversation

barriebyron
Copy link
Contributor

edits I didn't parse during the (quick!) cycle of #1237

this --release flag is a game-changer. Starport is growing up!

@barriebyron barriebyron requested review from fadeev and ilgooz June 11, 2021 19:54
@barriebyron barriebyron requested a review from lumtis as a code owner June 11, 2021 19:54
@barriebyron barriebyron self-assigned this Jun 11, 2021
@fadeev fadeev changed the title build.go suggested edits for optional --release flag docs: build.go suggested edits for optional --release flag Jun 13, 2021
Barrie Byron and others added 2 commits June 14, 2021 09:47
yes, I am learning! text wrap ourselves makes sense in a code file (TIL)

Co-authored-by: Denis Fadeev <denis@fadeev.org>
@barriebyron barriebyron requested a review from fadeev June 14, 2021 13:48
--release.targets (optional). Then, binaries built for chosen targets will appear
in your app's path under release/. You can add any number of targets in GOOS:GOARCH format.
If you don't provide any, a binary will be created for your own machine.
To build binaries for a release, use the optional --release flag. The app binaries
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

to make it clear, --release flag is actually required if you want the build command work in the release mode. But --release.targets flag is optional when you use --release.

Copy link
Contributor Author
@barriebyron barriebyron left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

see how we needed clarity!? I appreciate this back and forth @ilgooz
good suggestions, wdyt now?

applying changes since it's my PR

Co-authored-by: İlker G. Öztürk <ilkergoktugozturk@gmail.com>
Copy link
Contributor
@fadeev fadeev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@ilgooz ilgooz merged commit 239df42 into develop Jun 15, 2021
@ilgooz ilgooz deleted the build.go-PR1237-edit branch June 15, 2021 05:10
Jchicode pushed a commit to Jchicode/cli that referenced this pull request Aug 9, 2023
* suggested edits for the awesome release command

* Update starport/cmd/build.go

yes, I am learning! text wrap ourselves makes sense in a code file (TIL)

Co-authored-by: Denis Fadeev <denis@fadeev.org>

* Apply suggestions from code review

applying changes since it's my PR

Co-authored-by: İlker G. Öztürk <ilkergoktugozturk@gmail.com>

Co-authored-by: Denis Fadeev <denis@fadeev.org>
Co-authored-by: İlker G. Öztürk <ilkergoktugozturk@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants
0