feat: Profile image on user posts (palm.master)

[vladislavkeblysh]

Description

• Added profile image on user avatar posts

[openedx-webhooks]

Thanks for the pull request, @vladislavkeblysh!

What's next?

Please work through the following steps to get your changes ready for engineering review:

🔘 Get product approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

• If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
  • This process (including the steps you'll need to take) is documented here.
• If it doesn't, simply proceed with the next step.

🔘 Provide context

To help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:

• Dependencies

  This PR must be merged before / after / at the same time as ...

• Blockers

  This PR is waiting for OEP-1234 to be accepted.

• Timeline information

  This PR must be merged by XX date because ...

• Partner information

  This is for a course on edx.org.

• Supporting documentation
• Relevant Open edX discussion forum threads

🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.

🔘 Let us know that your PR is ready for review:

Who will review my changes?

This repository is currently maintained by @openedx/edx-infinity. Tag them in a comment and let them know that your changes are ready for review.

Where can I find more information?

If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:

• Overview of Review Process for Community Contributions
• Pull Request Status Guide
• Making changes to your pull request

When can I expect my changes to be merged?

Our goal is to get community contributions seen and reviewed as efficiently as possible.

However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:

• The size and impact of the changes that it introduces
• The need for product review
• Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.

[itsjeyd]

@vladislavkeblysh Thank you for this contribution!

[mphilbrick211]

Hi @vladislavkeblysh! Just flagging that there is a failing check.

[codecov]

Codecov Report

Attention: 1 lines in your changes are missing coverage. Please review.

Comparison is base (dcb0f9e) 92.38% compared to head (25221c9) 92.41%.
Report is 4 commits behind head on open-release/palm.master.

Files	Patch %	Lines
...c/discussions/discussions-home/FeedbackWrapper.jsx	50.00%	1 Missing ⚠️

Additional details and impacted files

@@                     Coverage Diff                      @@
##           open-release/palm.master     #573      +/-   ##
============================================================
+ Coverage                     92.38%   92.41%   +0.02%     
============================================================
  Files                           163      162       -1     
  Lines                          3297     3282      -15     
  Branches                        890      887       -3     
============================================================
- Hits                           3046     3033      -13     
+ Misses                          232      230       -2     
  Partials                         19       19              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[itsjeyd]

@vladislavkeblysh Looks like there are some coverage issues, can you have a look?

[vladislavkeblysh]

@itsjeyd The coverage issues are not related to the new code added in this PR. It seems like this has been carrying over from previous PRs.

[itsjeyd]

@vladislavkeblysh I see -- the line that the codecov check is complaining about wasn't changed in this PR. Thanks for checking.

That probably means it's OK to merge the changes as is, but it'll be up to engineering reviewers to make the final call on that.

[awais-ansari]

@vladislavkeblysh This change was intentional. This feature is still in product discussion.