-
Notifications
You must be signed in to change notification settings - Fork 8k
-
Notifications
You must be signed in to change notification settings - Fork 8k
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
Incorrect l10n.sourcecommit meta data #12128
Comments
cc. @mdn/yari-content-es @mdn/yari-content-ja |
@hochan222 |
It hasn't been merged yet, but you can check the automatically generated report file(source-commit-report.txt) when entering the When the command below fails, it is appended to the report file. git rev-list --count ${commitHash}..HEAD -- ${parentFilePath} |
Thank you so much! @hochan222 I'm looking that the es/glossary/index.md
|
I have created pull requests for the all files in |
@hochan222 |
2023/03/21 Errors are currently reported only for the paths below for all locales.
@mfuji09 All solved for
@Graywolf9 Git is only dealing with 40 digit hashes. Currently In the picture below, the source commit behind function I implemented handles only the 40-digit git hash correctly, so the page may not be able to track the Have a nice day :) |
Thank you so much! @hochan222 this should be done in #12315 |
Hello! @hochan222, #12315 has been merge, if there is something else to do, please let me know Thank you so much for all your work! |
Thank you all for your hard work. I checked the corrections you made. It's still under development, so it's not perfect, so I'll reopen it when I find a problem after the development is complete! Have a good day :) |
Issue
The hash value of the source commit in meta data is incorrect. In most cases, there is no hash in the history for the same file in the content repo.
Files Info
ja
es
Other supporting information
Check with the source-commit-report.txt file generated in the PR below.
mdn/yari#8338
The text was updated successfully, but these errors were encountered: