Various nits
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Sep 20 2020
[Bot Message]
One or more PR numbers were detected in the summary.
Links to those PRs have been inserted into the summary for reference.
[Bot Message]
One or more PR numbers were detected in the summary.
Links to those PRs have been inserted into the summary for reference.
[Bot Message]
One or more PR numbers were detected in the summary.
Links to those PRs have been inserted into the summary for reference.
[Bot Message]
One or more PR numbers were detected in the summary.
Links to those PRs have been inserted into the summary for reference.
Sep 19 2020
I don't think you read the summary. All of these variants are re-written to appear as the first variant, ensuring that these are both greppable and linked.
Sep 18 2020
Rebase
At least for the field size thing.
This doesn't really answer the question.
No. This makes history ungreppable.
In D7486#177985, @jasonbcox wrote:I noticed your test plan is rather complex and duplicates a lot of the logic in scripts/fetch_documentation.sh in the website repo. Consider improving it so it can take a local target instead of always pulling from the internet.
Put links directly in the text and remove References section
So far I have not been able to find another way of adding internal references to arbitrary places in a markdown file without using <a name="..."></a>. For instance the reference defined on line 199 is linked-to on line 9 with BIP143[[1]](#bip143)
remove leading $ for commands
I noticed your test plan is rather complex and duplicates a lot of the logic in scripts/fetch_documentation.sh in the website repo. Consider improving it so it can take a local target instead of always pulling from the internet. This should come in a separate diff of course.
Match more cases
[Bot Message]
One or more PR numbers were detected in the summary.
Links to those PRs have been inserted into the summary for reference.
Don't exclude all markdown, but adds an exception to the linter for the hard break special case
Add explicit check that HEAD has no changes from master
@bot build-tsan
I don't think this makes sense. Even if markdown supports trailing whitespace as a line break, it doesn't mean it's a good idea. Consider:
- Not linting this will now allow accidental trailing whitespaces.
- Trailing whitespace does not render well in all IDEs/editors.
- Intentional line breaks should be obvious, which trailing whitespace are not.
rebase
switch lock order on mempool_tests pointed by tsan
@bot build-tsan
use backslash as line breaks, to avoid lint issues with trailing whitespaces
squash another commit from the same PR (fix lines breaks)
Fix bad rebase
Rebase on top of D7473.
Fix rebase issue
Rebase on top of D7473
Rebase, depends on D7473