-
Notifications
You must be signed in to change notification settings - Fork 131
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
Too many updates #270
base: main
Are you sure you want to change the base?
Too many updates #270
Conversation
✅ Deploy Preview for nimble-elf-d9d491 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
72c82cf
to
0bb0c0d
Compare
- Update `.github/CODEOWNERS` - `build.yml`: run on `main` only - otherwise pull requests from `l10n/main` run build twice - `markdownlint.yml`: remove `branches` - `paths` already excludes pull requests from `l10n/main` - `settings.gradle`: build `latest` only - `update.ts`: don't add new versions to `settings.gradle`
- `incorrect-mod-id` - `no-horizontal-rules` - `no-html-line-breaks` - `no-trailing-punctuation-in-lists` - TODO: `max-one-sentence-per-line` --- - don't lint `versions` at all
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is a contender for the most unreviewable PR in the history of GitHub...
- name: no-trailing-whitespace | ||
message: "Don't use trailing whitespace" | ||
searchPattern: "/ +$/gm" | ||
replace: "" | ||
searchScope: code | ||
customRules: | ||
# TODO: add markdownlint-rule-max-one-sentence-per-line/rule.js |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this would be helpful for a few reasons:
- no longer worrying about line wraps
- longer/complicated sentences stick out
- crowdin doesn't show a confusing new line in the middle of source strings
it would however lead to a monstrous diff, so i avoided doing it here.
if i ever wanted to add it, the best way would be to render the markdown files after the sentences split and run a diff
on the built files to check for broken/changed formatting
image: { | ||
lazyLoading: true, | ||
}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
would appreciate feedback/testing on this
footer: { | ||
copyright: websiteResolver("footer.copyright").replace( | ||
"%s", | ||
`<a href=\"https://github.com/FabricMC/fabric-docs/blob/main/LICENSE\" target=\"_blank\" rel=\"noreferrer\">${websiteResolver("footer.license")}</a>` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
unsure what the best way to sanitize footer.license
is
a malicious translation could close the </a>
...
frontmatter.value.title | ||
? h("h1", { class: "vp-doc" }, frontmatter.value.title) | ||
: null, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is there ever a need for two different titles in <head>
and <body>
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, the homepage
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
doc-before
(line 35) only includes doc pages, not the homepage nor the 404 page
@@ -8,7 +8,7 @@ | |||
font-family: "Flag Emoji Polyfill"; | |||
unicode-range: U+1F1E6-1F1FF, U+1F3F4, U+E0062-E0063, U+E0065, U+E0067, | |||
U+E006C, U+E006E, U+E0073-E0074, U+E0077, U+E007F; | |||
src: url("./CountryFlagsPolyfill.woff2") format('woff2'); | |||
src: url("./CountryFlagsPolyfill.woff2") format("woff2"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if we used Noto Color Emoji we could embed it without shipping the binary file in the repo
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We dont need to include all emojis though, we only need the flags.
# Contribution Guidelines {#contributing} | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
every single markdown file will have at least a two-line diff.
I've also deleted some contributing
files which slipped through in versions
Tip
This diff page may have better performance than the review: main...its-miroma:fmc:framework
.github/CODEOWNERS
.github/workflows
:build.yml
:main
only, otherwise pull requests froml10n/main
run build twicemarkdownlint.yml
:branches
, aspaths
already excludes pull requests froml10n/main
workflow_dispatch
publish.yml
:ubuntu-24.04
settings.gradle
: buildlatest
onlyupdate.ts
: don't add new versions tosettings.gradle
h1
heading from$frontmatter.title
automatically#
headings.markdownlint-cli2.yaml
: enableMD025
markdownlint
rules:max-one-sentence-per-line
(not in here)incorrect-mod-id
no-horizontal-rules
no-html-line-breaks
translated
contributing.md
underversions