-
Notifications
You must be signed in to change notification settings - Fork 1
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
🏗️🐞 presubmit verification of Markdown fails consistently #580
Comments
Tracking the current state of our CI system's brokenness: evidently, additional effort(s) may be req'd beyond simply getting the Markdown verification script working again — — Codacy is likewise red and blocking our twin translation PRs (#568, #569) from being merged. Within the Codacy app, the culprits are clearly identified (e.g., failed quality gates); however, evidently, the apps' evals are not aligned w/ ours. We need to either inform that app of our preferences or simply remove its integration if it cannot be configured as we prefer as there's no justification left for its nagging about potential irrelevance. |
Judging by the stack trace, the failing plugin employed within the Markdown verification script —
— the statement from this line is embedded for closer examination below… Lines 52 to 72 in a1a5567
|
i have just now gone ahead and disabled Codacy (org-wide) seeing as how much of its checks would be repetitive or irrelevant, but we may find Codacy more useful once we are able to set aside the time necessary for it to be configured in such a way that it'd be a more suitable, dare i say (?), long-term solution |
this is done for now — we are closing… |
Apparently the CI's in need of repair most likely due to breaking changes affecting the APIs of the plugins employed by the script that evaluates Markdown files: “verify.md” —
— the context of the above error message viewable in the below image.
Self-assigned; however, this will not be receiving our final intended solution to the pre-submit testing of Markdown expected to be done by our CI; commits addressing this issue should not be expected to implement our final ideal solution…
How we expect to achieve our final ideal solution begins to be hashed out by myself in the following thread on the topic.
🔗:https://twitter.com/DerekNonGeneric/status/1660506159978086403
So, yes, this codebase will need to undergo “comprehensive deregulation”. We do not plan on having this be the location where rules are defined or enforced/triaged, but more on that a little later tonight once we can get a green CI for merging our translations…
The text was updated successfully, but these errors were encountered: