highperfocused/bitcoin
1
0
Fork 0
mirror of https://github.com/bitcoin/bitcoin.git synced 2025-05-06 18:01:03 +02:00
Code Issues Packages Projects Releases Wiki Activity

Merge bitcoin/bitcoin#22746: doc: Update GitHub documentation links

Browse Source 
470c6aa280f42558499db95b3ebca06a179d3514 doc: Update GitHub documentation links (Suriyaa Rocky Sundararuban)

Pull request description:

  Removing URL redirecting for GitHub documentation links.

ACKs for top commit:
  fanquake:
    ACK 470c6aa280f42558499db95b3ebca06a179d3514 - updates look correct.

Tree-SHA512: 5359aaddf1a1adabd0dc0e36cffcdb7b1ed83d9022314804655e010c84bf6143b7a2c8553a4e6c7793f02973868ad4b7554431ad61df82130ce47af74ebf0e99
This commit is contained in:
fanquake 2021-08-20 08:59:29 +08:00
commit 5b6104edf0
No known key found for this signature in database
GPG Key ID: 2EEB9F5CC09526C1
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
CONTRIBUTING.md
View File

@ -81,7 +81,7 @@ facilitates social contribution, easy testing and peer review.
To contribute a patch, the workflow is as follows: To contribute a patch, the workflow is as follows:
1. Fork repository ([only for the first time](https://help.github.com/en/articles/fork-a-repo)) 1. Fork repository ([only for the first time](https://docs.github.com/en/get-started/quickstart/fork-a-repo))
1. Create topic branch 1. Create topic branch
1. Commit patches 1. Commit patches
@ -182,7 +182,7 @@ for more information on helping with translations.
### Work in Progress Changes and Requests for Comments ### Work in Progress Changes and Requests for Comments
If a pull request is not to be considered for merging (yet), please If a pull request is not to be considered for merging (yet), please
prefix the title with [WIP] or use [Tasks Lists](https://help.github.com/articles/basic-writing-and-formatting-syntax/#task-lists) prefix the title with [WIP] or use [Tasks Lists](https://docs.github.com/en/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#task-lists)
in the body of the pull request to indicate tasks are pending. in the body of the pull request to indicate tasks are pending.
### Address Feedback ### Address Feedback
@ -386,7 +386,7 @@ about:
- It may be because your code is too complex for all but a few people, and those people - It may be because your code is too complex for all but a few people, and those people
may not have realized your pull request even exists. A great way to find people who may not have realized your pull request even exists. A great way to find people who
are qualified and care about the code you are touching is the are qualified and care about the code you are touching is the
[Git Blame feature](https://help.github.com/articles/tracing-changes-in-a-file/). Simply [Git Blame feature](https://docs.github.com/en/github/managing-files-in-a-repository/managing-files-on-github/tracking-changes-in-a-file). Simply
look up who last modified the code you are changing and see if you can find look up who last modified the code you are changing and see if you can find
them and give them a nudge. Don't be incessant about the nudging, though. them and give them a nudge. Don't be incessant about the nudging, though.
- Finally, if all else fails, ask on IRC or elsewhere for someone to give your pull request - Finally, if all else fails, ask on IRC or elsewhere for someone to give your pull request