-
Notifications
You must be signed in to change notification settings - Fork 223
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
reports: Add tarball hash #627
Comments
It can be omitted for the 2017 reports ; we'll create another issue to record those |
As the hashes are already done for 2018 data, please compute the hashes for the 2017 files. the field name we used was sha256sum iirc |
Ok, I understood what actually is to be done. I have to compute the hashes for 2017 files and display that computed hash on the webpage below the download link of the |
yup; so the downloader can verify they have the correct file, and the tarball (which isnt hosted on coala servers) hasnt been modified since the report was approved and merged. |
Hi @jayvdb ,I want to ask one more thing while working on this issue I have changed 9 files( 8 report files and 1 HTML file) so should I commit these files separately or together ? |
@KVGarg Commit them together. |
For now I'm committing with changes in default design :-) |
As per issue, I have added the computed sha256sum hash values for patch tarball for all the 2017 report files and display them on the project report webpage. Closes coala#627
As per issue, I have added the computed sha256sum hash values for patch tarball for all the 2017 report files and display them on the project report webpage. Only a part of hash value(first 7 characters only) is displayed on the webpage instead of entire hash value and a `copy to clipboard` button is added beside that hash value which will copy the entire hash value to the clipboard. and Removed some of space inconsistencies mentioned in travis tests. Closes coala#627
As per issue, I have added the computed sha256sum hash values for patch tarball for all the 2017 report files and display them on the project report webpage. Only a part of hash value(first 7 characters only) is displayed on the webpage instead of entire hash value and a `copy to clipboard` button is added beside that hash value which will copy the entire hash value to the clipboard. and Removed some of space inconsistencies mentioned in travis tests. Closes coala#627
As per issue, I have added the computed sha256sum hash values for patch tarball for all the 2017 report files and display them on the project report webpage. Only a part of hash value(first 7 characters only) is displayed on the webpage instead of entire hash value and a `copy to clipboard` button is added beside that hash value which will copy the entire hash value to the clipboard. and Removed some of space inconsistencies mentioned in travis tests. Formatted `style.css` by alpha ordering of properties. Maintained single quotes consistency in new Javascript code added. Closes coala#627
As per issue, I have added the computed sha256sum hash values for patch tarball for all the 2017 report files and display only the first seven characters of computed hash value on the project report webpage and the user can copy the full hash value by clicking on `clipboard` icon. Closes coala#627
The reports should include a tarball hash , as a variable in the yaml and this should be displayed beside the tarball in the HTML.
Mentors should check that the hash is correct before approving work reports.
The text was updated successfully, but these errors were encountered: