-
Notifications
You must be signed in to change notification settings - Fork 3
Add support for async templates #21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
bebraw
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you document the feature at readme? I think it's good to go after that.
|
@sapegin Any idea why the semantic release bot didn't catch this one? |
|
You can always check the logs ;-) |
|
There's no tag in the commit. |
|
Ah, I see. That's what the 🗣was about at #20 then? What's the correct way to trigger the bot manually? |
|
For example, make and empty commit ( |
|
Ok, got it. Just realized it wasn’t following the commit convention.
… On 29. Jan 2020, at 8.39, Artem Sapegin ***@***.***> wrote:
For example, make and empty commit (--allow-empty) with a correct tag (feat: XXXX).
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
|
🎉 This PR is included in version 2.2.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Simply: allow a
templatefunction to return a promise of a string.