Add Responsive Design #18
Merged
Conversation
This file contains 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
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #18 +/- ##
==========================================
- Coverage 96.81% 96.80% -0.02%
==========================================
Files 20 20
Lines 251 250 -1
Branches 20 20
==========================================
- Hits 243 242 -1
Misses 5 5
Partials 3 3
|
|
Your Render PR Server URL is https://ynab-custom-reports-pr-18.onrender.com. Follow its progress at https://dashboard.render.com/static/srv-cpbis48l6cac73e9836g. |
grantwforsythe
force-pushed
the
feat/add-responsive-styling
branch
from
9306039
to
768346e
Compare
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.
Pull Request Template
Title
[Provide a succinct and descriptive title for the pull request, e.g., "Improve caching mechanism for API calls"]
Type of Change
Description
[Provide a detailed explanation of the changes you have made. Include the reasons behind these changes and any relevant context. Link any related issues. For UI/UX changes, include a screenshot or recording of the changes.]
Testing
[Detail the testing you have performed to ensure that these changes function as intended. Include information about any added tests.]
Impact
[Discuss the impact of your changes on the project. This might include effects on performance, new dependencies, or changes in behavior.]
Additional Information
[Any additional information that reviewers should be aware of.]
Checklist