summaryrefslogtreecommitdiff
path: root/.github/workflows/ci.yaml
diff options
context:
space:
mode:
authorWouter Deconinck <wdconinc@gmail.com>2023-04-13 13:26:26 -0500
committerGitHub <noreply@github.com>2023-04-13 20:26:26 +0200
commitff319e98635fb952f1c26203c9041641f41687de (patch)
treec1f89d8c2eb986e2f346bf3061529f6139b73e8a /.github/workflows/ci.yaml
parentd918ae0bde903a2041a4c9d9edef5c59c63925cf (diff)
downloadspack-ff319e98635fb952f1c26203c9041641f41687de.tar.gz
spack-ff319e98635fb952f1c26203c9041641f41687de.tar.bz2
spack-ff319e98635fb952f1c26203c9041641f41687de.tar.xz
spack-ff319e98635fb952f1c26203c9041641f41687de.zip
Resolve `<include-fragment>` tags e.g. in github release pages (#36674)
This aims to resolve #34164 by resolving the <include-fragment> tags that GitHub has started using for their release pages, see https://github.github.io/include-fragment-element/. This feels a bit hacky but intended as a starting point for discussion. After reading a page during spidering, it first parses for include-fragments, gets them all, and treats them all as separate pages. Then it looks for href links in both the page itself and the fragments. Co-authored-by: Alec Scott <alec@bcs.sh>
Diffstat (limited to '.github/workflows/ci.yaml')
0 files changed, 0 insertions, 0 deletions