| Subject: | "dzil release" should fail if GithubMeta fails to find the remote |
Currently [githubMeta] just warns when it can not find the specified remote (or the default one). This is ok when developing, and this is convenient for contributors that work on a fork and that may not have named their remote the same as the maintainer.
However, this also allows the maintainer to shoot himself in the foot if he misses the warning while doing a release: the repository will not be set in META files.
So for 'dzil release', [GithubMeta] should die (log_fatal) instead of warning.
--
Olivier Mengué - http://perlresume.org/DOLMEN - https://gratipay.com/dolmen/
However, this also allows the maintainer to shoot himself in the foot if he misses the warning while doing a release: the repository will not be set in META files.
So for 'dzil release', [GithubMeta] should die (log_fatal) instead of warning.
--
Olivier Mengué - http://perlresume.org/DOLMEN - https://gratipay.com/dolmen/