-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Merge 2.8 release with master #1887
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
Conversation
* This solution is an hotfix for overrite issue came back on 2.8.0 version. What I did is checking the extension, and if it is null, adding .jpg suffix. Because commons files always have suffixes, and we should compare file names after adding suffixes. Othervise overrides are possible. * Check if file title includes an extension already, by checking if is there any dot in it. * Fix logic error * Add uncovered tests * Remove unecessary line breaks * Make Javadocs more explicit
* Versioning for v2.8.2 * Changelog for v2.8.2
* Refactor feedback and quiz to reduce possibility of NPE * Handle throwables in quiz checker * Minor refactoring
* Update changelog.md * Versioning for v2.8.3
Have resolved conflicts. Can be merged once the checks pass. |
All checks have passed. Merging it now. :) |
Ummm @maskaravivek , any idea why 2.8-release now has commits from master, with the latest being this PR? :/ https://github.com/commons-app/apps-android-commons/commits/2.8-release From what I can see this PR only merges the 2.8-release commits into master (which is correct), but why does the reverse happen? |
Title (required)
Merge 2.8 release with master