-
Notifications
You must be signed in to change notification settings - Fork 109
re-use createNormalInvoice in createAndPayNormalInvoiceWithBtc
#1008
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
|
@ZZiigguurraatt - could you just update the commit message to use the standard structure pls? 🙏 thanks |
Where do I find a definition of the standard structure so that I can do that properly? |
|
It's not linked specifically in all our projects but we try to follow these guidelines everywhere: https://github.com/lightningnetwork/lnd/blob/master/docs/code_contribution_guidelines.md |
f211384 to
571ef53
Compare
|
OK. how is the new commit message I've just changed to? |
I recommend you to also read how commit messages should be prefixed according to the golang convention docs, which is also linked in our contribution guidelines: https://go.dev/doc/contribute#commit_messages In practise, your commit message title here should be prefixed by the primary affected package ( But I'll let you decide on that phrasing as that's very nit-picky :) |
Redundant code is eliminated by re-using the function `createNormalInvoice` inside the function `createAndPayNormalInvoiceWithBtc`.
571ef53 to
ac464d6
Compare
|
OK, looks good now? |
small elimination of unnecessary redundant code