elastic / elastic/docs-tools

Plugin docgen with no changes shouldn't be considered a `FAILURE`

Open
#43 0 comments 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
Ruby
Stars
4
Forks
12
PR merge metrics
No merged PRs in 30d

Description

If the docgen job doesn't find any changes, it marks the build as `FAILURE` with info similar to:
```
On branch update_docs_1592941414
nothing to commit, working tree clean
```
This isn't a true failure. A successful build creates a PR, and it would be nice if there was some sort of messaging to let us know not to expect a PR. :-)

There's an easy workaround. It doesn't take a lot of time to search the console for `working tree clean`, so this doesn't need to be high priority.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.