Publishing is the creation of documents using page layout skills on a personal computer primarily for print. Desktop publishing software can generate layouts and produce typographic quality text and images comparable to traditional typography and printing.
The table ID is currently lost, but could be included by wrapping the table in a bookmark (probably via empty paragraphs before and after the table).
on latest develop, if I run:
go test
ERROR: 2020/10/09 16:43:21 oauth.go:148: viewOauthInit error: pretend unable to write state error
--- FAIL: TestViewOauthCallback (0.00s)
--- FAIL: TestViewOauthCallback/success (0.00s)
oauth_test.go:248:
Error Trace: oauth_test.go:248
Error: Received unexpected error:
/logi
Describe the bug
The diagram detailing when hooks (especially release lifecycle hooks) are invoked for each command are incredibly useful when writing a plugin or trying to understand how different plugins will behave together.
However, when tracing through the code, I've noticed the following inconsistency(ies) between the diagram and the
When the user saves a form it'd be nice to see some kind of visual feedback about what happened, instead of just reloading the page. The edit form notification box should be enabled by default for all the edit forms.
Expected Behavior
It should be possible to customize the header of the generated changelog (or omit it completely).
Current Behavior
The changelog header is hardcoded in https://github.com/lerna/lerna/blob/master/core/conventional-commits/lib/constants.js
Possible Solution
A `command.publish.changelogHea