As it stands pushing a single file in this regard isn't supported. Supporting such a thing would be considered a major version bump so there's a few things to consider.

• If this option did exist, would bothfolder andfiles be merged into a single parameter? Perhapspaths?
• Wouldpaths accept a single path, or multiple?
• If multiple, what happens when there's a file name conflict in the deployment directory that is created?
• What if one of the items in the path list is found, but another is not. Does the action fully fail or partially deploy what it could find?

I'm curious to learn more about your use case for this, and if there's a general consensus or not if this is something that multiple people want.

In the interim you can pushREADME.md into abuild folder by running a script before the deployment job runs, and then simply deploy from the folder that you create within the workflow.

name:Build and Deployon:[push]jobs:build-and-deploy:runs-on:ubuntu-lateststeps:      -name:Checkout 🛎️uses:actions/checkout@v2      -name:Generate deployment folderrun:|          mkdir build          mv README.md build/README.md      -name:Deploy 🚀uses:JamesIves/github-pages-deploy-action@v4with:branch:mainrepository-name:foobar/docfolder:build# Deploy the newly created "build" folder.

You can control what gets deployed just with .gitignore. If you want to have some files in your repo but not your deployment, then you could copy an alternative .gitignore over the top of the normal .gitignore as a step before the deploy action. That's what I do - my normal .gitignore ignores dist/, and my deployment .gitignore ignores src/.