Github Commit batch commit issues
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Hello,
I am attempting to build a workflow that utilize the "Github Commit" tool to write data to a static service. I believe I have all of my configurations successfully applied however it seems a sub-routine of the tool for batch commit is erroring out and I cannot figure out what part of my configure might be causing this issue, or if this is a general issue with the tool. I can perform a self commit without an issue, but when I want to pass a file it continues to error.
I know I can build something in python, so that is not the topic of the conversation, I would like to troubleshoot this tooling functionality.
Further diving into this, I receive 200's up until the macro tool does a POST on this end point [/repos/{owner}/{repo}/git/trees]. at this point I felt like I was getting out of my element a bit with how github functions with the directory creation, so I stopped digging. As best I can tell this seems like an issue with how the file path is being consumed and used for the github directory creation. not sure if anyone else ran into this issue previously.
 
 
 
 
  
 
 Self Commit
 
Solved! Go to Solution.
- Labels:
- Developer
- Developer Tools
- Macros
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Your download data has an error message -> must supply a tree... can you cut and paste the error message in this thread?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
DownloadData
{"message":"Must supply either tree.sha or tree.content. Request will be rejected if both are present.","documentation_url":"https://docs.github.com/rest/git/trees#create-a-tree","status":"422"}
DownloadHeaders
HTTP/1.1 422 Unprocessable Entity
Date: Mon, 24 Feb 2025 20:38:54 GMT
Content-Type: application/json; charset=utf-8
Content-Length: 194
X-OAuth-Scopes: admin:public_key, admin:repo_hook, repo, user, workflow, write:org, write:packages
X-Accepted-OAuth-Scopes:
github-authentication-token-expiration: 2025-03-26 17:32:34 UTC
X-GitHub-Media-Type: github.v3; format=json
x-github-api-version-selected: 2022-11-28
X-RateLimit-Limit: 5000
X-RateLimit-Remaining: 4973
X-RateLimit-Reset: 1740430387
X-RateLimit-Used: 27
X-RateLimit-Resource: core
Access-Control-Expose-Headers: ETag, Link, Location, Retry-After, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Used, X-RateLimit-Resource, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval, X-GitHub-Media-Type, X-GitHub-SSO, X-GitHub-Request-Id, Deprecation, Sunset
Access-Control-Allow-Origin: *
Strict-Transport-Security: max-age=31536000; includeSubdomains; preload
X-Frame-Options: deny
X-Content-Type-Options: nosniff
X-XSS-Protection: 0
Referrer-Policy: origin-when-cross-origin, strict-origin-when-cross-origin
Content-Security-Policy: default-src 'none'
Vary: Accept-Encoding, Accept, X-Requested-With
X-GitHub-Request-Id: xxxx:1B7D1A:25B445C:4BA50F6:xxxxxx
Server: github.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
What's in Filepath and Repo? I'm note 100% sure and would use CLI vs this tool for numerous reasons -> but my initial hunch is that the specific location you are trying to place the file in does not exist - or the file you are trying to place is not at that path on your laptop.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Ok, So I figured it out. The challenge was that I was putting an absolute URL path to the repo in my text input for "Repo" essentially "github.com/owner/repo" when it just needed to be "Repo". I guess I was confused by the fact that it was already asking for GitHub Repository Name under the Configure tab, so I assume/expected it needed to insert it on as a full repo path for the batch commit input line.
 
 
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Glad to see that this worked out.
