I do it manually although I probably should just write a commit hook to do
it.
I put it in the message itself because I think it's useful to have there in
case anyone is browsing the git log or in case we ever move away from
github.
Walden
On Thu, Apr 6, 2017 at 5:33 PM, Andrew Kofink
+1 from me :)
John Mitsch
Red Hat Engineering
(860)-967-7285
irc: jomitsch
On Thu, Apr 6, 2017 at 3:05 PM, Andrew Kofink wrote:
> I find myself copying/pasting issue numbers from GitHub PRs to a redmine
> url way too much every day. It takes a bit of time, and it's annoying
I find myself copying/pasting issue numbers from GitHub PRs to a redmine
url way too much every day. It takes a bit of time, and it's annoying as
well as easy to fix.
I've submitted this PR to comment on a newly submitted PR with links to the
associated issues in redmine:
On Thu, Apr 6, 2017 at 2:02 PM, Ewoud Kohl van Wijngaarden <
ew...@kohlvanwijngaarden.nl> wrote:
> On Wed, Apr 05, 2017 at 11:04:24AM -0400, Eric D Helms wrote:
> > Howdy,
> >
> > I have a number of Ansible modules that I have developed for managing
> > Katello entities and Foreman organizations.
On Wed, Apr 05, 2017 at 11:04:24AM -0400, Eric D Helms wrote:
> Howdy,
>
> I have a number of Ansible modules that I have developed for managing
> Katello entities and Foreman organizations. An Ansible module can be
> thought of as providing extentsibility and new functionality to Ansible
> roles
We still need to branch the Katello modules so that must happen first.
Other than that we haven't really discussed it but I do think we should
mirror this for the Katello modules for the same reason the foreman
modules dropped it: dependencies are dropping it and pinning on old
versions is