joshua/dash-docs
1
0
Fork 0
mirror of https://github.com/seigler/dash-docs synced 2025-07-27 01:36:13 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

events_notes_alerts: Fix link and excerpt

Browse source
This commit is contained in:
Will Binns 2017-03-26 07:14:17 -06:00
parent 5777df3240
commit e883503b86
No known key found for this signature in database
GPG key ID: 302EBEAEEB74A404
1 changed files with 5 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

10
docs/adding-events-release-notes-and-alerts.md
View file

@ -31,7 +31,7 @@ To create a new Bitcoin Core release, create a new file in the
recommend naming it after the release, such as `0.10.0.md` recommend naming it after the release, such as `0.10.0.md`
Then copy in the following YAML header (the part between the three dashes, ---): Then copy in the following YAML header (the part between the three dashes, ---):
~~~ ```
--- ---
# This file is licensed under the MIT License (MIT) available on # This file is licensed under the MIT License (MIT) available on
# http://opensource.org/licenses/MIT. # http://opensource.org/licenses/MIT.
@ -59,7 +59,6 @@ optional_magnetlink:
## (whitespace only) line, like the empty line before this list item. ## (whitespace only) line, like the empty line before this list item.
## ##
## 2. Place URLs inside angle brackets, like <http://bitcoin.org/bin> ## 2. Place URLs inside angle brackets, like <http://bitcoin.org/bin>
--- ---
``` ```
@ -91,9 +90,10 @@ is the particular version:
1. Create a new branch named `bitcoin-core-<VERSION>`. You can either 1. Create a new branch named `bitcoin-core-<VERSION>`. You can either
do this locally or in GitHub's web GUI. do this locally or in GitHub's web GUI.
2. Follow the instructions in the [Release Notes][] section to create a 2. Follow the instructions in the [Release
new release. You should leave the `optional_date` blank unless you Notes](https://github.com/bitcoin-dot-org/bitcoin.org/blob/master/docs/adding-events-release-notes-and-alerts.md#release-notes)
happen to know the date of the planned release. section to create a new release. You should leave the `optional_date` blank
unless you happen to know the date of the planned release.
3. Push the branch to the https://github.com/bitcoin-dot-org/bitcoin.org 3. Push the branch to the https://github.com/bitcoin-dot-org/bitcoin.org
repository so any contributor can edit it. **Don't** open a pull repository so any contributor can edit it. **Don't** open a pull