-
-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
Don't skip compliance on docs only PRs #24017
Conversation
We should make sure the docs linting happens
Hmm… Except that seems like a lot of unnecessary CI overhead. |
Will probably make it a lot slower because every one these pipelines needs to re-install dependencies because drone pipelines share nothing. I dislike introducing more pipelines because of this issue. |
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 don't have so many docs-only PRs, so this is fine imho.
Could introduce a optimized docs-only pipeline later that does the markdownlint only.
Such a docs-only pipeline could consist of single npx markdownlint-cli@$(jq -r '.devDependencies["markdownlint-cli"]' package.json) docs *.md |
Would you like this in this PR or a future one? |
Let's do later. It depends on |
No, I object to this change. I think we should have a separate pipeline for docs. |
Ok. I'll try again after https://gitea.com/gitea/test-env/pulls/22 lands. Just know that until then, we will push docs code to |
I guess a |
#24021 for that. |
We should make sure the docs linting happens