neo4j-documentation / neo4j-documentation/docs-refresh

Exit build on warning/failure

Open
#7 0 comments 0 reactions 2 assignees View on GitHub

@jexp is already working on this.

Since Sep 3, 2020.

:wrench: infrastructure
Dominant language
JavaScript
Stars
4
Forks
18
Avg merge
1m
Merged PRs (30d)
1

Description

If the build process returns an warnings or errors we should fail the build and if necessary create an issue or comment on the pull request. Some errors we should be catching are:

  • Unresolved/missing links in Antora
  • Missing attributes in content
  • Errors importing local/remote files

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.