Implement [skip-revcheck] to exclude a commit from consideration - #21
Implement [skip-revcheck] to exclude a commit from consideration#21fulldecent wants to merge 2 commits into
Conversation
|
@nilgun could you have a look at this, I don't really know how this version of the revcheck script works. |
|
What is the plan for getting every single author to be aware of this, and ensuring that it happens for every single commit that should be skipped (because even missing the tag from one commit for a file kind of defeats its usefulness)? |
|
I am requesting help to find where to document this new feature. This new feature is proposed specifically because I am making large commits that are touching many (300+) files and these changes on the English version do not require review by translators. Using this just for one commit makes it possible to continue using recheck after my proposed commit goes through. All other commits that use it will be an incremental benefit. And I think that translators who are downstream from any commits which should, but don't, use this |
|
The absence of en-commit-hash causes problems in scripts.
George Peter Banyard ***@***.***>, 23 Ağu 2021 Pzt,
23:08 tarihinde şunu yazdı:
…
@nilgun could you have a look at this, I don't really know how this version of the revcheck script works.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
|
|
The extreme case of the absence of the hash (Turkish file status):
Generated: 01 Sep 2021 19:22:48 |
|
Thanks for implementing this! |
|
Thank you for the review! I'm working to get a big commit in to take advantage of this... |
Discussion: php/doc-en#858 (comment)
This adds a new feature to the documentation translations checker:
Including the text:
in your commit message will exclude a commit from consideration in the tools at http://doc.php.net/revcheck.php
You should use this when:
I am not sure where to add that additional documentation meta notes. But I hope we can please document it as part of this PR.