go/goreleaser
go/goreleaser
1
0
Fork 0
mirror of https://github.com/goreleaser/goreleaser.git synced 2025-01-10 03:47:03 +02:00
Code Issues Releases Activity
79b7cebdae
goreleaser/www/docs/errors/dirty.md
Adam Harvey 0f79adca87
docs: fix wording (#3542) 
<!--

Hi, thanks for contributing!

Please make sure you read our CONTRIBUTING guide.

Also, add tests and the respective documentation changes as well.

-->


<!-- If applied, this commit will... -->

Fixes wording in the docs page about Git being in a dirty state.

<!-- Why is this change being made? -->

The goal is to improve the end-user reading of the instructions.

<!-- # Provide links to any relevant tickets, URLs or other resources
-->

...
2022-11-10 22:30:18 -03:00

743 B
Raw Blame History

Git is in a dirty state

GoReleaser requires a clean git state to work.

If you see this error, it means that something in your build process is either creating or editing files before GoReleaser is called. The error message should show you, which files were created/modified.

Here's an example error:

   ⨯ release failed after 0.02s error=git is currently in a dirty state
Please check in your pipeline what can be changing the following files:
 M modified.go
?? created.txt

Learn more at https://goreleaser.com/errors/dirty

From here on, you have a couple of options:

  • add the file to .gitignore (recommended if the file is temporary and/or generated);
  • change your build process to not touch any git tracked files.