Gauge Confluence v0.18.4

• #72 - Add workaround for linebreaks Confluence Cloud bug

Gauge Confluence v0.18.3

• #69 - Fix links in dry run Gauge spec

Gauge Confluence v0.18.2

Specify that any dir with specs can be published (#66)

* Specify that any dir with specs can be published

Adding the Gauge spec for this scenario revealed that Gauge (core Gauge,
not this Gauge Confluence plugin) currently has [a bug where the spec
details are not being propagated as they should be to documentation
plugins][1].  That means that the Gauge spec added in this test will
fail (which also means that the pull request containing this commit will
have a failed build and so cannot be merged) until the bug in core Gauge
is fixed.

[1]: https://github.com/getgauge/gauge/issues/2117

* Bump plugin patch version

Gauge Confluence v0.18.1

• #64 - Ensure plugin Git branch logic works on GitLab CI

Gauge Confluence v0.18.0

• #61 - Improve Space homepage content

Gauge Confluence v0.17.0

• #60 - Remove need for Space config vars in dry run mode

Gauge Confluence v0.16.1

• #59 - Publish the plugin's actual specs via CI/CD

Gauge Confluence v0.16.0

Remove the need to specify a Confluence Space key (#57)

* Remove the need to specify a Confluence Space key

Prior to this commit users of the plugin always had to specify the key
of the Confluence Space that they wanted to be published to (and to be
created if necessary).  This commit makes the `CONFLUENCE_SPACE_KEY`
Gauge configuration variable optional rather than mandatory.

If the `CONFLUENCE_SPACE_KEY` is not provided, the plugin will derive
the Space key to be used based on the remote Git repository URL. This
convention ensures that each Git repository has its own unique
Confluence space key derived from it, i.e. a one to one mapping between
each Git repository and its associated one to one space.

The recommended way to run the plugin now is not to provide the
`CONFLUENCE_SPACE_KEY` variable, and instead to rely on the plugin to
set it.  This is particularly useful in CI/CD for instance, as it
removes the need to set the Space key manually before being able to run
the plugin.

One use case for setting the `CONFLUENCE_SPACE_KEY` is if for whatever
reason you are unable to specify a Confluence user who has permission
to create Confluence Spaces.  By setting the `CONFLUENCE_SPACE_KEY` to
be an existing Space which someone (e.g. a Confluence admin) has
created for you, you will still be able to run the plugin even without
Confluence create space permissions.

* Refactor tests so git remote url can be specified

* Bump plugin minor version

Gauge Confluence v0.15.1

• #56 - Disable tests on Confluence Server temporarily

Gauge Confluence v0.15.0

• #53 - Add description to Space when it is created