1
0
mirror of https://github.com/goreleaser/goreleaser.git synced 2025-07-17 01:42:37 +02:00

Merge pull request #458 from goreleaser/docs-prettier

chore: checking markdown with prettier/prettier
This commit is contained in:
Carlos Alexandro Becker
2017-12-10 16:49:33 -02:00
committed by GitHub
14 changed files with 56 additions and 46 deletions

View File

@ -13,10 +13,9 @@ For more information, see the `CONTRIBUTING` guide.
Please paste the output of: Please paste the output of:
- `go version` * `go version`
- `uname -a` * `uname -a`
- `goreleaser --debug` * `goreleaser --debug`
### Steps to Reproduce ### Steps to Reproduce
@ -27,4 +26,3 @@ Please paste the output of:
**Expected behavior:** [What you expected to happen] **Expected behavior:** [What you expected to happen]
**Actual behavior:** [What actually happened] **Actual behavior:** [What actually happened]

View File

@ -2,12 +2,11 @@
<!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: --> <!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
- [ ] Bug fix (non-breaking change which fixes an issue) * [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality) * [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to change) * [ ] Breaking change (fix or feature that would cause existing functionality to change)
- [ ] I have read the **CONTRIBUTING** document. * [ ] I have read the **CONTRIBUTING** document.
- [ ] `make ci` passes on my machine. * [ ] `make ci` passes on my machine.
- [ ] My change requires a change to the documentation. * [ ] My change requires a change to the documentation.
- [ ] I have updated the documentation accordingly. * [ ] I have updated the documentation accordingly.
- [ ] I have added tests to cover my changes. * [ ] I have added tests to cover my changes.

View File

@ -7,6 +7,7 @@ services:
install: install:
- make setup - make setup
- gem install fpm - gem install fpm
- npm install -g prettier
- sudo apt-get update - sudo apt-get update
- sudo apt-get install --yes snapd rpm - sudo apt-get install --yes snapd rpm
- export PATH=/snap/bin:$PATH - export PATH=/snap/bin:$PATH

View File

@ -23,7 +23,7 @@ include:
Examples of unacceptable behavior by participants include: Examples of unacceptable behavior by participants include:
* The use of sexualized language or imagery and unwelcome sexual attention or * The use of sexualized language or imagery and unwelcome sexual attention or
advances advances
* Trolling, insulting/derogatory comments, and personal or political attacks * Trolling, insulting/derogatory comments, and personal or political attacks
* Public or private harassment * Public or private harassment
* Publishing others' private information, such as a physical or electronic * Publishing others' private information, such as a physical or electronic

View File

@ -3,7 +3,6 @@
By participating to this project, you agree to abide our [code of By participating to this project, you agree to abide our [code of
conduct](/CODE_OF_CONDUCT.md). conduct](/CODE_OF_CONDUCT.md).
## Setup your machine ## Setup your machine
`goreleaser` is written in [Go](https://golang.org/). `goreleaser` is written in [Go](https://golang.org/).
@ -38,7 +37,6 @@ A good way of making sure everything is all right is running the test suite:
$ make test $ make test
``` ```
## Test your change ## Test your change
You can create a branch for your changes and try to build from the source as you go: You can create a branch for your changes and try to build from the source as you go:
@ -55,7 +53,6 @@ $ make ci
Which runs all the linters and tests. Which runs all the linters and tests.
## Create a commit ## Create a commit
Commit messages should be well formatted. Commit messages should be well formatted.
@ -80,7 +77,6 @@ help others to generate their own changelog.
See #284 See #284
``` ```
## Submit a pull request ## Submit a pull request
Push your branch to your `goreleaser` fork and open a pull request against the Push your branch to your `goreleaser` fork and open a pull request against the

View File

@ -18,4 +18,4 @@ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE. SOFTWARE.

View File

@ -26,11 +26,13 @@ cover: test
# gofmt and goimports all go files # gofmt and goimports all go files
fmt: fmt:
find . -name '*.go' -not -wholename './vendor/*' | while read -r file; do gofmt -w -s "$$file"; goimports -w "$$file"; done find . -name '*.go' -not -wholename './vendor/*' | while read -r file; do gofmt -w -s "$$file"; goimports -w "$$file"; done
find . -name '*.md' -not -wholename './vendor/*' | xargs prettier --write
.PHONY: fmt .PHONY: fmt
# Run all the linters # Run all the linters
lint: lint:
gometalinter --vendor ./... gometalinter --vendor ./...
find . -name '*.md' -not -wholename './vendor/*' | xargs prettier -l
.PHONY: lint .PHONY: lint
# Run all the tests and code checks # Run all the tests and code checks

View File

@ -33,7 +33,6 @@ at https://goreleaser.com
[![goreleaser/goreleaser stargazers over time](https://starcharts.herokuapp.com/goreleaser/goreleaser.svg)](https://starcharts.herokuapp.com/goreleaser/goreleaser) [![goreleaser/goreleaser stargazers over time](https://starcharts.herokuapp.com/goreleaser/goreleaser.svg)](https://starcharts.herokuapp.com/goreleaser/goreleaser)
--- ---
Would you like to fix something in the documentation? Feel free to open an [issue](https://github.com/goreleaser/goreleaser/issues). Would you like to fix something in the documentation? Feel free to open an [issue](https://github.com/goreleaser/goreleaser/issues).

View File

@ -19,8 +19,24 @@ that and rewrote the whole thing in Go.
## Installing Goreleaser ## Installing Goreleaser
There are three ways to get going. There are three ways to get going install GoReleaser:
1. Install Goreleaser via go get (`goreleaser` command will be globally available) `go get github.com/goreleaser/goreleaser` ### Using go get
1. On a Mac use [Homebrew](https://github.com/goreleaser/homebrew-tap).
1. Install directly [from the binaries](https://github.com/goreleaser/goreleaser/releases/latest). ```sh
go get github.com/goreleaser/goreleaser
```
### Using homebrew
```sh
brew install goreleaser/tap/goreleaser
```
> Check the [tap source](https://github.com/goreleaser/homebrew-tap) for
> more details.
## Manually
Download your preferred flavor from the [releases page](https://github.com/goreleaser/goreleaser/releases/latest) and install
manually.

View File

@ -70,9 +70,9 @@ This configuration will generate `tar` archives, each containing an additional
file called `drum-roll.licence.txt`. file called `drum-roll.licence.txt`.
The archives will be located in the `dist` folder: The archives will be located in the `dist` folder:
- `./dist/drum-roll_windows_64-bit.tar.gz` * `./dist/drum-roll_windows_64-bit.tar.gz`
- `./dist/drum-roll_macOS_64-bit.tar.gz` * `./dist/drum-roll_macOS_64-bit.tar.gz`
- `./dist/drum-roll_Tux_64-bit.tar.gz` * `./dist/drum-roll_Tux_64-bit.tar.gz`
Next, you need to export a `GITHUB_TOKEN` environment variable, which should contain a Next, you need to export a `GITHUB_TOKEN` environment variable, which should contain a
GitHub token with the `repo` scope selected. GitHub token with the `repo` scope selected.

View File

@ -17,7 +17,6 @@ Here is how to do it with Travis CI:
By default, GoReleaser will create its artifacts in the `./dist` folder. By default, GoReleaser will create its artifacts in the `./dist` folder.
If you must, you can change it by setting it in the `.goreleaser.yml` file: If you must, you can change it by setting it in the `.goreleaser.yml` file:
```yaml ```yaml
# .goreleaser.yml # .goreleaser.yml
dist: another-folder-that-is-not-dist dist: another-folder-that-is-not-dist
@ -25,7 +24,7 @@ dist: another-folder-that-is-not-dist
## Using the `main.version` ## Using the `main.version`
GoReleaser always sets a `main.version` *ldflag*. GoReleaser always sets a `main.version` _ldflag_.
You can use it in your `main.go` file: You can use it in your `main.go` file:
```go ```go

View File

@ -2,7 +2,7 @@
title: Homebrew title: Homebrew
--- ---
After releasing to GitHub, GoReleaser can generate and publish a *homebrew-tap* After releasing to GitHub, GoReleaser can generate and publish a _homebrew-tap_
recipe into a repository that you have access to. recipe into a repository that you have access to.
The `brew` section specifies how the formula should be created. The `brew` section specifies how the formula should be created.

View File

@ -7,7 +7,7 @@ GoReleaser supports building and pushing artifacts into Artifactory.
## How it works ## How it works
You can declare multiple Artifactory instances. You can declare multiple Artifactory instances.
All binaries generated by your `builds` section will be pushed to All binaries generated by your `builds` section will be pushed to
each configured Artifactory. each configured Artifactory.
@ -24,8 +24,8 @@ artifactories:
Prerequisites: Prerequisites:
- A running Artifactory instances * A running Artifactory instances
- A user + password / API key with grants to upload an artifact * A user + password / API key with grants to upload an artifact
### Target ### Target
@ -45,14 +45,14 @@ http://artifacts.company.com:8081/artifactory/example-repo-local/goreleaser/1.0.
Support variables: Support variables:
- Version * Version
- Tag * Tag
- ProjectName * ProjectName
- Os * Os
- Arch * Arch
- Arm * Arm
*Attention*: Variables _Os_, _Arch_ and _Arm_ are only supported in upload mode `binary`. _Attention_: Variables _Os_, _Arch_ and _Arm_ are only supported in upload mode `binary`.
### Password / API Key ### Password / API Key

View File

@ -2,11 +2,11 @@
title: Links title: Links
--- ---
- Follow the progress on the [GitHub repository](https://github.com/goreleaser/goreleaser) * Follow the progress on the [GitHub repository](https://github.com/goreleaser/goreleaser)
- Follow [@caarlos0](https://twitter.com/caarlos0) on Twitter for updates * Follow [@caarlos0](https://twitter.com/caarlos0) on Twitter for updates
- [Slack](https://gophers.slack.com/messages/goreleaser/) to chat about GoReleaser, * [Slack](https://gophers.slack.com/messages/goreleaser/) to chat about GoReleaser,
questions, etc. Join using [this link](https://invite.slack.golangbridge.org/) questions, etc. Join using [this link](https://invite.slack.golangbridge.org/)
- [Contributing Guidelines](https://github.com/goreleaser/goreleaser/blob/master/CONTRIBUTING.md) * [Contributing Guidelines](https://github.com/goreleaser/goreleaser/blob/master/CONTRIBUTING.md)
This project adheres to the Contributor Covenant This project adheres to the Contributor Covenant
[code of conduct](https://github.com/goreleaser/goreleaser/blob/master/CODE_OF_CONDUCT.md). [code of conduct](https://github.com/goreleaser/goreleaser/blob/master/CODE_OF_CONDUCT.md).