ActionGitHubUpdated September 2026

How do I delete a file from a GitHub repository?

Short answer: You can delete file in GitHub by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the GitHub Delete File action to a workflow, map its 5 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Delete File in GitHub — start free All 23 GitHub actions

Delete File in GitHub — start free

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Owner owner	string	Required	GitHub repository owner — the user or organization login (the part before / in owner/repo URLs).
Repository repo	string	Required	GitHub repository name — the part after / in owner/repo URLs. Not the full URL.
File Path path	string	Required	File Path. Example: docs/readme.md
Commit Message message	string	Required	Commit Message. Example: Remove obsolete file
Branch branch	string	Optional	Git branch name.

Sample request

{
  "owner": "e.g. octocat",
  "repo": "e.g. hello-world",
  "path": "e.g. docs/readme.md",
  "message": "e.g. Remove obsolete file",
  "branch": "e.g. main"
}

Returns

{
  "commit": {
    "sha": "def456",
    "message": "Delete file"
  }
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Delete File.

Any of these apps can fire this action as part of a workflow.

Google Sheets → GitHub

2 Google Sheets triggers

HubSpot → GitHub

18 HubSpot triggers

FAQ

Questions about Delete File.

What does the Delete File action do in GitHub?

Deletes a file from a GitHub repository in a single commit. The file's SHA is auto-fetched, so you only need to provide the path.

What inputs does Delete File require?

Required: Owner, Repository, File Path, Commit Message. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if GitHub returns an error?

The run history shows the failed step with its input and the error message GitHub returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does Delete File support batch operations?

Run Delete File inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within GitHub's rate limits.

More actions