Create jekyll-gh-pages.yml (IDFGH-12955)

[LLotme]

..

[github-actions[bot]]

	Warnings
:warning:	Some issues found for the commit messages in this PR: the commit message "Create jekyll-gh-pages.yml": summary looks empty type/action looks empty the commit message "feat: upgrade axios from 0.21.4 to 1.7.2": probably contains Jira ticket reference (5-4358). Please remove Jira tickets from commit messages. body's lines must not be longer than 100 characters the commit message "feat: upgrade vue-router from 3.6.5 to 4.3.2": probably contains Jira ticket reference (5-4358). Please remove Jira tickets from commit messages. body's lines must not be longer than 100 characters the commit message "feat: upgrade vuetify from 1.5.24 to 3.6.8": probably contains Jira ticket reference (5-4358). Please remove Jira tickets from commit messages. body's lines must not be longer than 100 characters the commit message "fix: tools/requirements/requirements.ci.txt to reduce vulnerabilities": probably contains Jira ticket reference (CERTIFI-3164749, CERTIFI-5805047, CERTIFI-7430173, IDNA-6597975, REQUESTS-5595532). Please remove Jira tickets from commit messages. the commit message "fix: tools/requirements/requirements.ci.txt to reduce vulnerabilities": probably contains Jira ticket reference (REQUESTS-6928867, URLLIB3-7267250, ZIPP-7430899). Please remove Jira tickets from commit messages. the commit message "fix: tools/requirements/requirements.ci.txt to reduce vulnerabilities": probably contains Jira ticket reference (URLLIB3-7267250). Please remove Jira tickets from commit messages. the commit message "fix: tools/requirements/requirements.ci.txt to reduce vulnerabilities": probably contains Jira ticket reference (ZIPP-7430899). Please remove Jira tickets from commit messages. the commit message "fix: tools/requirements/requirements.core.txt to reduce vulnerabilities": probably contains Jira ticket reference (ZIPP-7430899). Please remove Jira tickets from commit messages. the commit message "fix: tools/requirements/requirements.docs.txt to reduce vulnerabilities": probably contains Jira ticket reference (CAIROSVG-3366799, PILLOW-5918878, PILLOW-6043904, PILLOW-6182918, PILLOW-6219984, PILLOW-6219986, PILLOW-6514866, REQUESTS-6928867, SETUPTOOLS-3180412). Please remove Jira tickets from commit messages. the commit message "fix: tools/requirements/requirements.docs.txt to reduce vulnerabilities": probably contains Jira ticket reference (CAIROSVG-3366799). Please remove Jira tickets from commit messages. the commit message "fix: tools/requirements/requirements.docs.txt to reduce vulnerabilities": probably contains Jira ticket reference (PILLOW-5918878, PILLOW-6043904, PILLOW-6182918, PILLOW-6219984, PILLOW-6219986, PILLOW-6514866, REQUESTS-6928867, SETUPTOOLS-3180412, SETUPTOOLS-7448482, URLLIB3-7267250, ZIPP-7430899). Please remove Jira tickets from commit messages. the commit message "fix: tools/requirements/requirements.docs.txt to reduce vulnerabilities": probably contains Jira ticket reference (PILLOW-5918878, PILLOW-6043904, PILLOW-6182918, PILLOW-6219984, PILLOW-6219986, PILLOW-6514866, REQUESTS-6928867). Please remove Jira tickets from commit messages. the commit message "fix: tools/requirements/requirements.docs.txt to reduce vulnerabilities": probably contains Jira ticket reference (PILLOW-5918878, PILLOW-6043904, PILLOW-6182918, PILLOW-6219984, PILLOW-6219986, PILLOW-6514866, REQUESTS-6928867). Please remove Jira tickets from commit messages. the commit message "fix: tools/requirements/requirements.docs.txt to reduce vulnerabilities": probably contains Jira ticket reference (SETUPTOOLS-3180412). Please remove Jira tickets from commit messages. the commit message "fix: tools/requirements/requirements.docs.txt to reduce vulnerabilities": probably contains Jira ticket reference (SETUPTOOLS-3180412). Please remove Jira tickets from commit messages. the commit message "fix: tools/requirements/requirements.docs.txt to reduce vulnerabilities": probably contains Jira ticket reference (SETUPTOOLS-7448482). Please remove Jira tickets from commit messages. the commit message "fix: tools/requirements/requirements.docs.txt to reduce vulnerabilities": probably contains Jira ticket reference (URLLIB3-7267250). Please remove Jira tickets from commit messages. the commit message "fix: tools/requirements/requirements.docs.txt to reduce vulnerabilities": probably contains Jira ticket reference (ZIPP-7430899). Please remove Jira tickets from commit messages. the commit message "fix: tools/requirements/requirements.gdbgui.txt to reduce vulnerabilities": probably contains Jira ticket reference (DNSPYTHON-6241713). Please remove Jira tickets from commit messages. the commit message "fix: tools/requirements/requirements.gdbgui.txt to reduce vulnerabilities": probably contains Jira ticket reference (DNSPYTHON-6241713). Please remove Jira tickets from commit messages. the commit message "fix: tools/requirements/requirements.gdbgui.txt to reduce vulnerabilities": probably contains Jira ticket reference (JINJA2-6150717, JINJA2-6809379, WERKZEUG-6035177, WERKZEUG-6808933). Please remove Jira tickets from commit messages. the commit message "fix: tools/requirements/requirements.gdbgui.txt to reduce vulnerabilities": probably contains Jira ticket reference (JINJA2-6150717, JINJA2-6809379). Please remove Jira tickets from commit messages. the commit message "fix: tools/requirements/requirements.gdbgui.txt to reduce vulnerabilities": probably contains Jira ticket reference (WERKZEUG-6035177, WERKZEUG-6808933, ZIPP-7430899). Please remove Jira tickets from commit messages. the commit message "fix: tools/requirements/requirements.gdbgui.txt to reduce vulnerabilities": probably contains Jira ticket reference (WERKZEUG-6035177, WERKZEUG-6808933). Please remove Jira tickets from commit messages. the commit message "fix: tools/requirements/requirements.gdbgui.txt to reduce vulnerabilities": probably contains Jira ticket reference (ZIPP-7430899). Please remove Jira tickets from commit messages. the commit message "fix: tools/requirements/requirements.pytest.txt to reduce vulnerabilities": probably contains Jira ticket reference (SETUPTOOLS-3180412, SETUPTOOLS-7448482). Please remove Jira tickets from commit messages. the commit message "fix: tools/requirements/requirements.pytest.txt to reduce vulnerabilities": probably contains Jira ticket reference (SETUPTOOLS-7448482). Please remove Jira tickets from commit messages. the commit message "fix: tools/requirements/requirements.pytest.txt to reduce vulnerabilities": probably contains Jira ticket reference (URLLIB3-7267250). Please remove Jira tickets from commit messages. the commit message "fix: tools/requirements/requirements.pytest.txt to reduce vulnerabilities": probably contains Jira ticket reference (ZIPP-7430899). Please remove Jira tickets from commit messages. Please fix these commit messages - here are some basic tips: follow Conventional Commits style correct format of commit message should be: <type/action>(<scope/component>): <summary>, for example fix(esp32): Fixed startup timeout issue allowed types are: change,ci,docs,feat,fix,refactor,remove,revert,test sufficiently descriptive message summary should be between 20 to 72 characters and start with upper case letter avoid Jira references in commit messages (unavailable/irrelevant for our customers) TIP: Install pre-commit hooks and run this check when committing (uses the Conventional Precommit Linter).
:warning:	Please consider squashing your 66 commits (simplifying branch history).
:warning:	The Pull Request description looks very brief, please check if more details can be added.

👋 Hello LLotme, we appreciate your contribution to this project!

---

📘 Please review the project's Contributions Guide for key guidelines on code, documentation, testing, and more.

---

🖊️ Please also make sure you have read and signed the Contributor License Agreement for this project.

---

Click to see more instructions ...

This automated output is generated by the PR linter DangerJS, which checks if your Pull Request meets the project's requirements and helps you fix potential issues.

DangerJS is triggered with each push event to a Pull Request and modify the contents of this comment.

Please consider the following:
- Danger mainly focuses on the PR structure and formatting and can't understand the meaning behind your code or changes.
- Danger is not a substitute for human code reviews; it's still important to request a code review from your colleagues.
- Resolve all warnings (⚠️ ) before requesting a review from human reviewers - they will appreciate it.
- To manually retry these Danger checks, please navigate to the Actions tab and re-run last Danger workflow.

Review and merge process you can expect ...

We do welcome contributions in the form of bug reports, feature requests and pull requests via this public GitHub repository.

This GitHub project is public mirror of our internal git repository

1. An internal issue has been created for the PR, we assign it to the relevant engineer.
2. They review the PR and either approve it or ask you for changes or clarifications.
3. Once the GitHub PR is approved, we synchronize it into our internal git repository.
4. In the internal git repository we do the final review, collect approvals from core owners and make sure all the automated tests are passing.
- At this point we may do some adjustments to the proposed change, or extend it by adding tests or documentation.
5. If the change is approved and passes the tests it is merged into the default branch.
5. On next sync from the internal git repository merged change will appear in this public GitHub repository.

Generated by :no_entry_sign: dangerJS against 9397a6106637f748f036654e89f4ad7c951e066d

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

:white_check_mark: LLotme
:x: snyk-bot
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[dobairoland]

I'm sorry but I don't see the point behind this PR. The Jekyll part was already rejected by closing https://github.com/espressif/esp-idf/pull/13895. As for the Python package dependencies, versions should not be handled in those files. We use constraint files as documented at https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-guides/tools/idf-tools.html.