Add keyword coercion (Keyword symbol) in #duct/env

[arichiardi]

Implements #38.

[atomist[bot]]

Commit messages of this repository should follow the seven rules of a great Git commit message, as mentioned in the project's contributing guidelines. It looks like there's a few issues with the commit messages in this pull request:

• The commit message subject is over 50 characters.

[atomist[bot]]

Commit messages of this repository should follow the seven rules of a great Git commit message, as mentioned in the project's contributing guidelines. It looks like there's a few issues with the commit messages in this pull request:

• The commit message subject is over 50 characters.

[atomist[bot]]

Commit messages of this repository should follow the seven rules of a great Git commit message, as mentioned in the project's contributing guidelines. It looks like there's a few issues with the commit messages in this pull request:

• The commit message body has a line over 72 characters.

[weavejester]

Let's make it Keyword instead.

[arichiardi]

@weavejester anything else we need to do for merging this one?

[weavejester]

I don't get notified about new commits, so it's often worth adding a comment, otherwise I won't know if there have been changes :)

Can you change the commit message to:

Add keyword coercion to #duct/env (fixes #38)

There's no need to add any more to the commit message.

[arichiardi]

I can definitely do that, FWIW the second part is content and won't appear in git log with --pretty=oneline - it is usually recommended to have head + content. In any case doing it and writing you back when done

[arichiardi]

Ok done

[weavejester]

FWIW the second part is content and won't appear in git log with --pretty=oneline - it is usually recommended to have head + content.

I'd generally agree, but in this case it doesn't add any useful information so should be omitted.