abiosoft / abiosoft/caddy-git

Pulling `{latest}` via WebHook

Offen
#97 4 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
Vorherrschende Sprache
Go
Sterne
206
Forks
42
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Beschreibung

```
# caddy -version
Caddy 0.11.1 (non-commercial use only)
```

Considering the following `Caddyfile`:

```
http://www.example.com {
root /web/www.example.com/public
git https://github.com/example/example.com {
hook /path TOKEN
branch {latest}
path ..
then /hugo --destination=/web/www.example.com/public --cleanDestinationDir
}
}

http://beta.example.com {
root /web/beta.example.com/public
git https://github.com/example/example.com {
hook /path TOKEN
branch master
path ..
then /hugo --destination=/web/beta.example.com/public --cleanDestinationDir
}
}

```
The expected behaviour is:
* On a `commit`/`push` to the repo beta.example.com will be updated.
* On a `commit`/`push` to the repo www.example.com will NOT be updated. (Caddy log: `2018/12/06 12:00:55 github webhook ignored. Error: found different branch master`).
* On a `tag`/`push --tags` to the repo beta.example.com will be updated with no effect
* On a `tag`/`push --tags` to the repo www.example.com will be updated to latest version.

Effective behaviour is:
* `commit`/`push` works as expected.
* `tag`/`push --tags` gives the following error for BOTH instances (www/beta):
`2018/12/06 12:02:44 github webhook ignored. Error: found different branch v1.0.4` where v1.0.4 is the latest tag.

A restart of Caddy results in the expected behaviour.

Is this a bug or is my understanding of the plugin wrong?

Beitragsleitfaden

Für dieses Repository ist kein Beitragsleitfaden indexiert

Bewertung

Dieses Issue wurde noch nicht bewertet.

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.