It is possible to update a current file?

I am trying to update a post that I created with staticman for my jekyll site.

Here is my config.

editaddons:
  allowedFields:
    [
      'title',
      'body',
      'curselink',
      'wowilink',
      'websitelink',
      'gitlink',
      'image',
      'status',
      'categories',
      'editorsname',
      'editreason',
    ]
  branch: 'develop'
  commitMessage: 'Edit Addon'
  format: 'frontmatter'
  generatedFields:
    date:
      type: date
    slug:
      type: slugify
      options:
        field: title
    layout: addon
    draft: false
  filename: '{fields.slug}'
  moderation: true
  name: 'xxxxxxxxsic.com'
  path: '_addons'
  requiredFields: ['title', 'body', 'editorsname', 'editreason']
  transforms:
    email: md5
    body: 'frontmatterContent'

And the error I am getting when trying to overright the same file.

{  
   "success":false,
   "rawError":{  
      "message":"{\"message\":\"Invalid request.\\n\\n\\\"sha\\\" wasn't supplied.\",\"documentation_url\":\"https://developer.github.com/v3/repos/contents/#create-or-update-a-file\"}",
      "statusCode":422
   },
   "errorCode":"GITHUB_FILE_ALREADY_EXISTS"
}

Is it possible to oversight? I am starting to think the sha message could be a key, but I am unsure how to proceed.

Thank you for any help.

[alexwaibel]

Question seems to have been answered by @VincentTam. Resolved.

[VincentTam]

Sorry for super-late reply.

@danieldreke I see your point. I think OP’s problem described in the question context doesn’t require the feature request, which would have been much better to be put in a separate issue because of the one-issue-one-problem principle. Given that we’ve already started the discussion about the FR, I’ll add my comment to the pile.

With respect to the recently established GPDR, I see a motive to ask the collector of static comments, which are a form of data, for a modification. However, let’s think about the target users:

1. Dev’ers/Prog’ers: they have Git* acct, so they can simply jump into the corresponding auto-gen’d Git* issue and ask the site owner for changing. That would fail if the source code for the static site isn’t public.
2. Others who don’t write code: examples incl writers, commentators, etc. I doubt if they would bother to take the steps above to have their comments changed.

It seems technically possible, but who practically needs that?