WIP Libscholar 47 update links in static pages #1192
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ization - Remove SimpleCov/Coveralls setup from spec_helper.rb to prevent double initialization - Consolidate all coverage setup in rails_helper.rb - Add simplecov-lcov and configure LCOV formatter for CircleCI - Use SimpleCov.formatters (plural) with all three formatters: HTML, LCOV, and Coveralls - Configure formatters before starting SimpleCov to ensure proper setup
- Replace SimpleCov.start with Coveralls.wear! to properly handle parallel test execution - Configure formatters before Coveralls.wear! starts SimpleCov - Maintains LCOV formatter for CircleCI upload
…/RoMEO, and Berkeley copyright links
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Not yet ready
Fixes #issuenumber ; refs #issuenumber
Present short summary (50 characters or less)
More detailed description, if necessary. Try to be as descriptive as you can: even if you think that the PR content is obvious, it may not be obvious to others. Include tracebacks if helpful, and be sure to call out any bits of the PR that may be work-in-progress.
Description can have multiple paragraphs and you can use code examples inside:
Changes proposed in this pull request:
*
*
*