-
Notifications
You must be signed in to change notification settings - Fork 110
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
Prepare 0.11.3 release #3167
Prepare 0.11.3 release #3167
Conversation
=== Do not change lines below === { "chain": [], "cmd": "./tools/link_issues_CHANGELOG", "exit": 0, "extra_inputs": [], "inputs": [], "outputs": [], "pwd": "." } ^^^ Do not change lines above ^^^
Er, these are merge commits: 4eff996 (BF: Allow datalad commands not requiring git-annex changes to operate on read-only filesystem, 2019-02-15) and 4eff996 (BF: Allow datalad commands not requiring git-annex changes to operate on read-only filesystem, 2019-02-15). Guess GitHub has changed their style of the default merge subject? |
Codecov Report
@@ Coverage Diff @@
## master #3167 +/- ##
=========================================
+ Coverage 90.8% 90.8% +<.01%
=========================================
Files 249 249
Lines 32781 32784 +3
=========================================
+ Hits 29766 29769 +3
Misses 3015 3015
Continue to review full report at Codecov.
|
Nope, I changed the way I did merges today. |
Oh, I see. I've witnessed a trail being blazed.
I can't parse that. |
sorry -- was on the phone and laptop fix was still being WiP (recent fall to the floor broke one of the screen hinges a bit). What I meant is that may be we should set a habbit to adjust all merge messages to be close to the ones we want to see in the changelog? |
=== Do not change lines below === { "chain": [], "cmd": "./tools/link_issues_CHANGELOG", "exit": 0, "extra_inputs": [], "inputs": [], "outputs": [], "pwd": "." } ^^^ Do not change lines above ^^^
Oh, poor laptop :[
No, please use whatever form you prefer. For my changelog purposes, they are fine because they're picked out just the same by
Thanks!
Done (just linked to the second PR number). |
Will do touchups locally, thank you @kyleam ! |
Since 0.11.2