Removed gh-pages-deploy-action from release.yml

[ThaungThanHan]

Description

I have removed github-pages-deploy-action from release.yml. Fixes: #2465

Deploy Preview

(https://github.com/ThaungThanHan/paragon/blob/9ffc37a18fc183a9b882a2cdc7a4a07661d35c43/.github/workflows/release.yml#L39)

Merge Checklist

• If your update includes visual changes, have they been reviewed by a designer? Send them a link to the Netlify deploy preview, if applicable.
• Does your change adhere to the documented style conventions?
• Do any prop types have missing descriptions in the Props API tables in the documentation site (check deploy preview)?
• Were your changes tested using all available themes (see theme switcher in the header of the deploy preview, under the "Settings" icon)?
• Were your changes tested in the example app?
• Is there adequate test coverage for your changes?
• Consider whether this change needs to reviewed/QA'ed for accessibility (a11y). If so, please add wittjeff and adamstankiewicz as reviewers on this PR.

Post-merge Checklist

• Verify your changes were released to NPM at the expected version.
• If you'd like, share your contribution in #show-and-tell.
• 🎉 🙌 Celebrate! Thanks for your contribution.

[openedx-webhooks]

Thanks for the pull request, @ThaungThanHan! Please note that it may take us up to several weeks or months to complete a review and merge your PR.

Feel free to add as much of the following information to the ticket as you can:

• supporting documentation
• Open edX discussion forum threads
• timeline information ("this must be merged by XX date", and why that is)
• partner information ("this is a course on edx.org")
• any other information that can help Product understand the context for the PR

All technical communication about the code itself will be done via the GitHub pull request interface. As a reminder, our process documentation is here.

Please let us know once your PR is ready for our review and all tests are green.

⚠️ We can't start reviewing your pull request until you've submitted a signed contributor agreement or indicated your institutional affiliation. Please see the CONTRIBUTING file for more information. If you've signed an agreement in the past, you may need to re-sign. See The New Home of the Open edX Codebase for details.

Once you've signed the CLA, please allow 1 business day for it to be processed. After this time, you can re-run the CLA check by adding a comment here that you have signed it. If the problem persists, you can tag the @openedx/cla-problems team in a comment on your PR for further assistance.

[netlify]

✅ Deploy Preview for paragon-openedx ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	9ffc37a
🔍 Latest deploy log	https://app.netlify.com/sites/paragon-openedx/deploys/64bd42f785034900081a8657
😎 Deploy Preview	https://deploy-preview-2467--paragon-openedx.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[codecov]

Codecov Report

Patch and project coverage have no change.

Comparison is base (314b116) 91.39% compared to head (9ffc37a) 91.39%.
Report is 3 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #2467   +/-   ##
=======================================
  Coverage   91.39%   91.39%           
=======================================
  Files         234      234           
  Lines        4161     4161           
  Branches     1001     1001           
=======================================
  Hits         3803     3803           
  Misses        351      351           
  Partials        7        7           

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

[e0d]

Hi @ThaungThanHan , we need to have a valid Contributor License Agreement (CLA) in place for all contributions. See the welcome message above for the details about how to enroll. The process is different depending upon whether you are making this contribution as an individual or on behalf of your employer.

Also I notice there are some commit-lint failures. Please note that we use conventional commits across Open edX projects. You can read about the details here. Can you please amend your commit messages to follow our standard?

[mphilbrick211]

Hi @ThaungThanHan , we need to have a valid Contributor License Agreement (CLA) in place for all contributions. See the welcome message above for the details about how to enroll. The process is different depending upon whether you are making this contribution as an individual or on behalf of your employer.

Also I notice there are some commit-lint failures. Please note that we use conventional commits across Open edX projects. You can read about the details here. Can you please amend your commit messages to follow our standard?

Hi @ThaungThanHan! Just checking to see if you were able to submit your CLA form? Please let me know if you have any questions. Thanks!

[mphilbrick211]

Hi @ThaungThanHan! Just checking in to see if you plan to pursue this pull request?

[mphilbrick211]

Hi @ThaungThanHan! I'm going to close this for now. If you would like to pursue in the future, we can reopen. Thanks!

[openedx-webhooks]

@ThaungThanHan Even though your pull request wasn’t merged, please take a moment to answer a two question survey so we can improve your experience in the future.

[openedx-webhooks]

@ThaungThanHan Even though your pull request wasn’t merged, please take a moment to answer a two question survey so we can improve your experience in the future.