[WIP] Ensure Python 3.5 is installable on Ubuntu 20.04 in GitHub Actions

[Copilot]

• Analyze repository structure and existing CI configuration
• Verify Python 3.5 availability for Ubuntu 20.04 in actions/python-versions
• Create .github/workflows directory structure
• Create GitHub Actions workflow file using Ubuntu 20.04
• Configure workflow to install Python 3.5 and dependencies
• Validate workflow YAML syntax
• Test workflow to ensure it works correctly

Original prompt

use the ubuntu 20.04 on the github action to ensure that python3.5 is installable .
https://raw.githubusercontent.com/actions/python-versions/main/versions-manifest.json

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[luzfcb]

@copilot on the branch pelican, use the ubuntu 20.04 on the github actions ( .github/workflows ) to ensure that python3.5 is installable . https://raw.githubusercontent.com/actions/python-versions/main/versions-manifest.json

[Copilot]

@copilot on the branch pelican, use the ubuntu 20.04 on the github actions ( .github/workflows ) to ensure that python3.5 is installable . https://raw.githubusercontent.com/actions/python-versions/mai...

I've created the GitHub Actions workflow at .github/workflows/build.yml that uses ubuntu-20.04 and Python 3.5. The workflow is configured to run on the pelican branch and ensures Python 3.5.10 is installable (verified in the actions/python-versions manifest). Commit: e756cf0

[luzfcb]

@copilot do not create a new yml file, change all the actions that already exists on .github/workflows/ of the pelican branch

[Copilot]

@copilot do not create a new yml file, change all the actions that already exists on .github/workflows/ of the pelican branch

I checked the pelican branch and there's no .github/workflows/ directory with existing workflows. The only CI configuration I found is .travis.yml. Should I:

1. Create the workflow on the pelican branch (instead of this feature branch), or
2. Update/migrate the .travis.yml to GitHub Actions?

Could you clarify which approach you'd prefer?