-
Notifications
You must be signed in to change notification settings - Fork 336
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
Consider not always generating pages from PR and issue templates #2358
Comments
Would you like to turn this into a PR? I don't think this needs to be an option, since I doubt it is useful to anyone. |
I can do that. Could you clarify if you consider this a user-facing change that should be mentioned in |
I'd say it's user facing enough to be mentioned. |
hsloot
added a commit
to hsloot/pkgdown
that referenced
this issue
Oct 30, 2023
hadley
added a commit
that referenced
this issue
Apr 12, 2024
Fixes #2358 Co-authored-by: Hadley Wickham <[email protected]>
SebKrantz
pushed a commit
to SebKrantz/pkgdown
that referenced
this issue
Jun 1, 2024
Fixes r-lib#2358 Co-authored-by: Hadley Wickham <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
The documentation of
build_home
statesI cannot think of a situation where it makes sense to always generate pages for pull request templates or issues templates, commonly located in the
.github/
folder; see creating a pull request template.Proposition
Add configuration
meta$home$build_gh_templates
as perand in
build_home_md()
Alternative
Maybe on a broader scale, one could think of a file
.pkgdownignore
to control which files/directories should be ignored by pkgdown.Context
pkgdown/R/build-home-md.R
Lines 5 to 9 in d5432a4
The text was updated successfully, but these errors were encountered: