Staging #172
Merged
Staging #172
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
styled mentee profile to wireframe
updated skills to display per the wireframe
switch JSON to multipart form
updated the urls
Mentee session
Session signup
setup the session form
mentor session filter working
commented out text notifications for now
…dding Mm 63 edit feature so mentors adding
…nd-read-me MM-8 Created the FE readme
…1485c053ece76bcf8281150638 [Snyk] Upgrade @mui/material from 5.14.0 to 5.14.1
…e6c36c2f540b6d4ad6adbf804d [Snyk] Upgrade @mui/icons-material from 5.14.0 to 5.14.1
…7aa45c4c84eb088a33e3010ac0 [Snyk] Upgrade @sentry/react from 7.59.2 to 7.59.3
Snyk has created this PR to upgrade @sentry/react from 7.59.3 to 7.60.0. See this package in npm: https://www.npmjs.com/package/@sentry/react See this project in Snyk: https://app.snyk.io/org/gitlukew/project/3fe86609-be8f-4a37-91a9-1e13c3ada34b?utm_source=github&utm_medium=referral&page=upgrade-pr
…ress Mm105 implement cypress
Snyk has created this PR to upgrade @mui/material from 5.14.1 to 5.14.2. See this package in npm: https://www.npmjs.com/package/@mui/material See this project in Snyk: https://app.snyk.io/org/gitlukew/project/3fe86609-be8f-4a37-91a9-1e13c3ada34b?utm_source=github&utm_medium=referral&page=upgrade-pr
Snyk has created this PR to upgrade @mui/icons-material from 5.14.1 to 5.14.3. See this package in npm: https://www.npmjs.com/package/@mui/icons-material See this project in Snyk: https://app.snyk.io/org/gitlukew/project/3fe86609-be8f-4a37-91a9-1e13c3ada34b?utm_source=github&utm_medium=referral&page=upgrade-pr
…ble at a selected time then a message displays telling the user
…f30f30d47e8e64da556592ddf6 [Snyk] Upgrade @sentry/react from 7.59.3 to 7.60.0
…410754c5513630b07e5ddb997b [Snyk] Upgrade @mui/material from 5.14.1 to 5.14.2
…466f4342867ac1e4a679011741 [Snyk] Upgrade @mui/icons-material from 5.14.1 to 5.14.3
added skills to EditProfile.js
added conditional on sessions signup page so if no mentors are availa…
…dropdown menus disabled
mm60 added alert message for empty skills array. working now to make …
✅ Deploy Preview for staging-momentors ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for momentum-mentors ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
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
1. Targeted Issue
(The first step to a good solution is knowing the problem. Please link the issue here.)
Issue #... or
Ticket #...
2. Overview of Solution
(You've put in the hard work, now's your chance to tell us about it. What's your solution in a nutshell?)
3. Tools Used
(Share the tools, libraries, or techniques you've used in your solution.)
4. Testing Strategy
(No code is complete without tests. Outline what you've tested and how.)
5. Future Implications
(Let's anticipate potential effects of your changes. Are there any potential issues down the line?)
6. Screenshots
(A picture is worth a thousand words. Include screenshots of your changes if relevant.)
7. Code Reviewers
(Who else is in the loop? Mention your team or other contributors here.)
Before you go...
Big high-fives for your incredible pull request! We're thrilled to have you as a contributor! Our team will dig into your proposed changes and give you some feedback or merge them if they're good to go. Your contributions mean the world to us!