go/goreleaser
go/goreleaser
1
0
Fork 0
mirror of https://github.com/goreleaser/goreleaser.git synced 2025-03-19 20:57:53 +02:00
Code Issues Releases Activity

Merge pull request #477 from bpicode/master

Browse Source 
fix typos in documentation
This commit is contained in:
Carlos Alexandro Becker 2017-12-20 09:22:25 -02:00 committed by GitHub
commit 4ca8faa862
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
5 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/075-sign.md
View File

@ -10,7 +10,7 @@ Signing works in combination with checksum files and it is generally sufficient
to sign the checksum files only.
The default is configured to create a detached signature for the checksum files
with [GunPG](https://www.gnupg.org/) and your default key. To enable signing
with [GnuPG](https://www.gnupg.org/) and your default key. To enable signing
just add
```yaml

2
docs/110-snapcraft.md
View File

@ -54,7 +54,7 @@ snapcraft:
drumroll:
# If your app requires extra permissions to work outside of its default
# confined space, delcare them here.
# confined space, declare them here.
# You can read the documentation about the available plugs and the
# things they allow:
# https://snapcraft.io/docs/reference/interfaces).

2
docs/115-release.md
View File

@ -45,7 +45,7 @@ changelog:
filters:
# commit messages matching the regexp listed here will be removed from
# the changelog
# Default is emtpy
# Default is empty
exclude:
- '^docs:'
- typo

4
docs/125-artifactory.md
View File

@ -13,7 +13,7 @@ each configured Artifactory.
If you have only one Artifactory instance,
the configuration is as easy as adding the
upload target and a usernameto your `.goreleaser.yml` file:
upload target and a username to your `.goreleaser.yml` file:
```yaml
artifactories:
@ -59,7 +59,7 @@ _Attention_: Variables _Os_, _Arch_ and _Arm_ are only supported in upload mode
Your configured username needs to be authenticated against your Artifactory.
The password or API key will be stored in a environment variable.
The confgured name of your Artifactory instance will be used.
The configured name of your Artifactory instance will be used.
With this way we support auth for multiple instances.
This also means that the `name` per configured instance needs to be unique
per goreleaser configuration.

2
docs/140-ci.md
View File

@ -1,5 +1,5 @@
---
title: Continous Integration
title: Continuous Integration
---
You may want to setup your project to auto-deploy your new tags on